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,
(gdb) c
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. Perhaps it isn't
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, gdb
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 thread.
On Tue, 9 Sep 2003, Marco Gerards wrote:
Why is writing required? Is that a requirement for setting a active
translator? (That is, IIRC, what libdiskfs does).
(I always had the idea that I can set a translator on any node I own)
Write access is not a requirement for setting an
Greg Buchholz [EMAIL PROTECTED] writes:
On Mon, 8 Sep 2003, Marco Gerards wrote:
#boot -D/cdrom servers.boot /dev/hd2
That's seems correct to me. Using -d to pause seems a good idea
here. (That's what I meant with the pause to attach).
Okay, when I attach to the boot
On Tue, Sep 09, 2003 at 07:34:11PM +0200, Marco Gerards wrote:
Marcus Brinkmann [EMAIL PROTECTED] writes:
On Mon, Sep 08, 2003 at 11:10:35PM +0200, Marco Gerards wrote:
/hurd/iso9660fs.statis --multi-boot-command yada,yada,yada
/hurd/ld.so.1 /hurd/exec
bye
This is weird. Is
Greg Buchholz [EMAIL PROTECTED] writes:
Has anyone out there ever used a serial console for debugging a
hurd translator at boot time? I'm looking for the gdb debug stub
functions (getDebugChar, exceptionHandler, etc) that can be used before
the hurd is up and running (and after Mach
On Mon, 8 Sep 2003, Marcus Brinkmann wrote:
The way you'd normally do that is using the boot command and booting a
second Hurd system in parallel to the first one. Then you can attach gdb to
the processes inside the second Hurd.
I tried the boot command, but my setup didn't fail in
On Mon, Sep 08, 2003 at 05:02:15PM +0100, Greg Buchholz wrote:
Has anyone out there ever used a serial console for debugging a
hurd translator at boot time? I'm looking for the gdb debug stub
functions (getDebugChar, exceptionHandler, etc) that can be used before
the hurd is up and
Greg Buchholz [EMAIL PROTECTED] writes:
On Mon, 8 Sep 2003, Marcus Brinkmann wrote:
The way you'd normally do that is using the boot command and booting a
second Hurd system in parallel to the first one. Then you can attach gdb to
the processes inside the second Hurd.
I tried the
On Tue, 9 Sep 2003, Marcus Brinkmann wrote:
On Mon, Sep 08, 2003 at 11:10:35PM +0200, Marco Gerards wrote:
This is weird. Is /hurd/exec on the fs. Is there a /server/* ? Attach
gdb to the fs. to see what it its loading.
Yes, there is a /hurd/exec, and I have a /server directory
12 matches
Mail list logo
