Re: remote debugging stubs (EXC_BAD_ACCESS)

2003-09-14 Thread Jeroen Dekkers
On Sat, Sep 13, 2003 at 10:46:57PM +0200, Marco Gerards wrote: > Greg Buchholz <[EMAIL PROTECTED]> writes: > > [Switching to thread 202.1] > > (gdb) info threads > > * 1 thread 202.1 0x0808d2dc in mach_msg_trap () > > (gdb) break diskfs_init_diskfs > > Breakpoint 1 at 0x804b235: file init-init.c,

Re: remote debugging stubs (EXC_BAD_ACCESS)

2003-09-13 Thread Marco Gerards
Greg Buchholz <[EMAIL PROTECTED]> writes: [...] > warning: Can't modify tracing state for pid 202: No signal thread I'm not sure about how signals *exactly* work on the Hurd, but AFAIK every task is also a server and listens for signal. If there is no thread (to listen for signals) you can't se

Re: remote debugging stubs (EXC_BAD_ACCESS)

2003-09-12 Thread Marco Gerards
Greg Buchholz <[EMAIL PROTECTED]> writes: > On Wed, 10 Sep 2003, Marco Gerards wrote: > > > Greg Buchholz <[EMAIL PROTECTED]> writes: > > > Program received signal EXC_BAD_ACCESS, Could not access memory. > > > 0x0806c203 in _hurd_ports_use() > > > > Have a look at all thread and where they are.

Re: remote debugging stubs (EXC_BAD_ACCESS)

2003-09-10 Thread Greg Buchholz
On Wed, 10 Sep 2003, Marco Gerards wrote: > Greg Buchholz <[EMAIL PROTECTED]> writes: > > Program received signal EXC_BAD_ACCESS, Could not access memory. > > 0x0806c203 in _hurd_ports_use() > > Have a look at all thread and where they are. Perhaps it isn't in > _hurd_ports_use, but in another th

Re: remote debugging stubs (EXC_BAD_ACCESS)

2003-09-10 Thread Marco Gerards
Greg Buchholz <[EMAIL PROTECTED]> writes: > > Greg Buchholz <[EMAIL PROTECTED]> writes: > > > Okay, when I attach to the boot process, I can set breakpoints > > > fine, but when I continue, I get the following message (in gdb)... > > > Can't wain for pid 174: No child processes. > > > > > > ...t

Re: remote debugging stubs (EXC_BAD_ACCESS)

2003-09-10 Thread Greg Buchholz
> Greg Buchholz <[EMAIL PROTECTED]> writes: > > Okay, when I attach to the boot process, I can set breakpoints > > fine, but when I continue, I get the following message (in gdb)... > > Can't wain for pid 174: No child processes. > > > > ...then when I hit enter to continue the paused "boot", g