Re: importing symbols from unsupported BFD target

[Tavis Ormandy <taviso@sdf.lonestar.org>]

Daniel Jacobowitz <drow@false.org> wrote:

> On Tue, Jun 30, 2009 at 06:59:06PM +0200, Tavis Ormandy wrote:
> > This basically works, `info address symname`, `b symname`, `x/i symname`
> > all work, but `info symbol address` fails, and stacktraces, info
> > breakpoints, etc, etc are not symbolised.
> > 
> > Can anyone suggest what I might be missing?
> 
> I think you're going to have to create sections in the file; this sounds
> like it's going to be specific to ABS symbols.  A NOBITS (bss) section is
> probably fine though it may need to be marked executable too.
> 

Ahh, you were absolutely right :-)

It took some massaging to convince ld to create the output I wanted, but it
does appear to have worked, and I can now do basic remote debugging of the
windows kernel using gdb.

And the backtrace is now symbolised correctly:

Breakpoint 23, 0x805c517d in PsImpersonateClient ()
(gdb) bt
#0  0x805c517d in PsImpersonateClient ()
#1  0x805ece9b in SeImpersonateClientEx ()
#2  0x8059a68a in NtImpersonateClientOfPort ()
#3  0xee392c01 in ?? ()
...

Which looks exactly right. Really pleased I can work on this from within
gdb.

Thanks, Tavis.

-- 
-------------------------------------
taviso@sdf.lonestar.org | finger me for my pgp key.
-------------------------------------------------------