[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Debugging glibc / startup stuff via a subhurd

From: Roland McGrath
Subject: Re: Debugging glibc / startup stuff via a subhurd
Date: Sun, 11 Feb 2007 12:39:36 -0800 (PST)

> Program received signal EXC_BAD_ACCESS, Could not access memory.
> 0x000168f2 in ?? ()
> (gdb) bt
> #0  0x000168f2 in ?? ()
> Cannot access memory at address 0xbeffffe4
> (gdb) info threads
> * 1 thread 1005.1  0x000168f2 in ?? ()
> (gdb) disassemble 
> No function contains program counter for selected frame.

Use x/10i $pc to see the code there when disassemble doesn't know what
bounds to use.  When gdb is confused, you can figure out what's loaded
where and use add-symbol-file with some manual calculations.  I'm sure the
details of that are floating around somewhere.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]