RE: No line number info debugging kernel modules with gdb 6.6.90.20070926-cvs (gdb 6.7 branch)

["Jon Ringle" <JRingle@vertical.com>]

Jim Blandy wrote:
> Well, I'm pretty confused.
> 
> For starters, the output from 'maint print symbols' includes a line
> 325, but the output from 'readelf -wil' shows no such line.
> 
> Then, GDB has set the breakpoint on vert_dst_nopage_mmap at
> 0xbf1342b4, but 'maint print symbols' says that function's block
> covers the addresses 0xbf13434c..0xbf1343b4, which doesn't cover the
> breakpoint's address.

The output that I got from 'maint print symbols' and the output from
'readelf -wil' were from two different runs and I think I may have
inserted some code between these two runs that may explain this
inconsistency. I can do get you fresh output of all of it if you'd like.

> 
> The more inconsistencies you find, the more information you have about
> the bug, I guess, but I can't see the unifying story here.
> 
> One last thing: John, could you 'set debug remote 1' before connecting
> to your target, and see if it's sending a 'qOffsets' packet?  If it
> does, then that gets applied to symfile_objfile, which in your case
> would have been dstdrv.ko.  But I'd expect any qOffsets received from
> the kernel to be meant for vmlinux; the remote stub has no idea you've
> loaded dstdrv.ko.

Will do this tonight.

> 
> If that's what's going on, then it might help to connect to the target
> before doing the add-symbol-file.

Ok