Quote:
Originally Posted by jotd
yeah, it's very good that it uses msys2 because i can integrate it in my native toolchains & cmds. After another test, now I don't need cygwin anymore (debugger works without it too so good work)
Today I could connect the debugger to WinUAE with success. Only problem is that the debugger reports that no symbols are found. But there ARE symbols. I've used -g -O0 options and nm reports that there are symbols...
Did I miss something?
Code:
C:\DATA\jff\data\C++\games\Bagman>m68k-amigaos-nm bagman | more
000012ec D _DOSBase
00005264 D _GfxBase
0000526c D _IntuitionBase
000012f4 D _MathIeeeDoubBasBase
00005274 D _MathIeeeDoubTransBase
0000527c D _MathIeeeSingBasBase
000574de T _SDL_AddTimer
00056efe T _SDL_CreateRGBSurface
000572dc T _SDL_Delay
000571ee T _SDL_DisplayFormat
00057058 T _SDL_FillRect
...
gdb failing to load symbols:
Code:
C:\DATA\jff\data\C++\games\Bagman>m68k-amigaos-gdb bagman
GNU gdb (GDB) 8.3.50.191012-223043-git
Copyright (C) 2019 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Type "show copying" and "show warranty" for details.
This GDB was configured as "--host=x86_64-pc-msys --target=m68k-amigaos".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
<http://www.gnu.org/software/gdb/documentation/>.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from bagman...
(No debugging symbols found in bagman)
(gdb)
|
there are symbols: function names
and symbols: debug information
despite the use of symbol for both it's different kind of information.
So it seems you are creating object files containing debug infos, do you also link properly?
That's either m68k-amigaos-gcc -g *.o -o exefile
or m68k-amigaos-ld -amiga-debug-hunk ... -o exefile
And a hint here: instead of copying the file to the Amiga use m68k-amigaos-strip exefile -o path/to/amiga/exefile since there is no use of loading the debug info into the Amiga's ram.