I have a VC compiled application. It loads dll with gdb
debug info. After loading the program stops, I attach to
the process, clear the existing symbol table and type
something like:
add-symbol-file c:\vhpi_for_ahdl.dll 0x17D31000 -s .data
0x17D3300
or
add-symbol-file vhpi_for_ahdl.dll 0x17D31000 -s .data
0x17D33000 -s .rdata 0x17D34000 -s .bss
0x17D35000 -s .edata 0x17D36000 -s .idata
0x17D37000 -s .reloc 0x17D38000 -s .stab
0x17D39000 -s .stabstr 0x17D3A000
Then I wat to set a breakpionf for some line. break
file::line.
1) Sometimes it sets breakpoint to adress 0x17D31xxx
but usually at 0x10000xxxx.
If I put breakpoint like break *17d31xxx it sets the
breakpoint and shows the info about correct file and line.
2) Another problem - gpf when trying to execute symbol-
file with no parameters after attaching to process.
Workarounds: 1) type break file:number, see the last
digits of the adress, clear breakpoint, add breakpoint to
the recalculated adress.
2) execute symbol-file for another dummy dll then
execute it to the needed dll.
Testcase: will come in 1(2) days.
gdb 5.2.1 mingw edition
mailto:slimering_backstab2hotmail.com
Logged In: YES
user_id=629594
mailto:slimering_backstab@hotmail.com
Logged In: YES
user_id=15438
I've put it on my round tuit list to take a look at gdb.
Logged In: YES
user_id=15438
Newer versions of gdb exist.