Yes, kdb is documented in GNU Mach Reference. But I'm not aware of
documented precise instructions how to make good report for GNU
Mach panic, e.g. where to set breakpoints and what kdb commands to
be run for the report.
That depends on a case by case basis, like all debugging.
On Sun, Mar 06, 2005 at 01:42:27AM +0100, Alfred M. Szmidt wrote:
> Always tell us what function the EIP really is.
Probably not that helpful...
#v+
$ addr2line -fe gnumach 0x11a07e
Debugger
./kern/debug.c:102
#v-
#v+
cat -n kern/debug.c | grep -C 10 ^\ \ \ 102
92 asm("ta 0x81");
Alfred M. Szmidt wrote:
It is already documented in the --help output for configure, and in
the GNU Mach documentation, so there is no need to mention this on the
wiki.
Yes, kdb is documented in GNU Mach Reference. But I'm not aware of
documented precise instructions how to make good report for G
It is already documented in the --help output for configure, and in
the GNU Mach documentation, so there is no need to mention this on the
wiki. It would be nice if someone could take the information stored
on the wiki, and incoperate it into the Hurd or GNU Mach manuals. The
wiki is not a substi
Thomas Schwinge wrote:
Another GNU Mach panic:
#v+
panic: zalloc: zonethreads exhausted
Kernel Breakpoint trap, eip 0x11a07e
Stopped at 0x11a07d: int $3
db> continue
panic: zalloc: zone kalloc.256 exhausted
Kernel Breakpoint trap, eip 0x11a07e
Stopped at 0x11a07d: int $3
db> reset
#v-
How have you
Always tell us what function the EIP really is.
You haven't told use what arguments for glibc you used to compile it.
___
Bug-hurd mailing list
Bug-hurd@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-hurd
