Hi Markus, On Wed, 2008-04-09 at 09:45 +0200, Markus Franke wrote: > Hi Kieran, > well, this doesn't help in my case. Besides, I provide the symbol file > already on startup of gdb for example by calling: > > ---snip--- > m68k-bdm-gdb uClinux-dist/user/ping/ping.gdb > ---snap---
Sorry, I maybe I didn't make this bit clear Don't provide the symbols at the startup of gdb, as that will load them at the default address 0x00. > > But even after explicitly loading the symbol file again as you > proposed I get: > (gdb) b main > Cannot access memory at address 0x5ee > ---snap--- Loading after is no good, as it already has the symbols loaded at the initial address. > > I have the feeling that there might be something wrong with my *.gdb > symbol files?!?!? I think GDB would have told you if your symbol file didn't contain debug information. > Thanks for the hint anyway and good luck for your breakpoint problem. ;-) > > With best regards, > Markus > I've been talking to one of the GDB dev's on IRC, and he's pointed me towards gdb-6.7.1/gdb/gdbserver/linux-low.c the part that does the offsets is in linux_read_offsets(). If it doesn't have the correct values defined for PTrace to obtain them, then you'll probably have to find them out yourself, or as it was in my case, extend the kernel implementation for PTrace to support the required PT_TEXT_ADDR PT_TEXT_END_ADDR and PT_DATA_ADDR. I've done this now, and it lets me load as normal without playing around loading symbol files after with offsets. It also knows about all the data segments now so I can back trace etc... Next on the todo list : Breakpoints! but its getting there. -- Hope this helps. Kieran Bingham _______________________________________________ uClinux-dev mailing list [email protected] http://mailman.uclinux.org/mailman/listinfo/uclinux-dev This message was resent by [email protected] To unsubscribe see: http://mailman.uclinux.org/mailman/options/uclinux-dev
