Re: Debugging glibc / startup stuff via a subhurd

[Thomas Schwinge]

Hello!

On Fri, Feb 09, 2007 at 09:36:55PM +0100, I wrote:
> So, I got glibc 2.5 natively built [...]

> #v+ W3
> $ sudo gdb /var/tmp/one.full/hurd/exec
> [...]
> (gdb) set solib-absolute-prefix /var/tmp/one.full
> (gdb) attach 854
> Attaching to program `/var/tmp/one.full/hurd/exec', pid 854
> warning: Can't modify tracing state for pid 854: No signal thread
> Can't fetch registers from thread 1: No such thread
> #v-
> 
> [...]
> 
> #v+ W3
> (gdb) continue
> Continuing.
> warning: Can't wait for pid 854: No child processes
> 
> 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.
> #v-

In my previous email the implicit question was whether someone has an
idea about how to continue with this.  If not then I'll try some code
staring w.r.t. the relro stuff.


Regards,
 Thomas

signature.asc
Description: Digital signature