On Mon, Jun 12, 2006 at 07:47:32PM +0100, Robert Watson wrote: > > > It looks like there is a problem with the stack trace from kgdb. Is there > any chance your kernel and kernel.debug are out of sync? Today I removed DDB and GDB from the kernel, because with it no kernel dumps were created. To build it, i used -DNO_CLEAN. Can this cause the kernel to get out of sync with kernel.debug? > Does this box have a serial port? If so, you might want to try setting up > a serial console for it with a null modem cable to an adjacent box. DDB > may be able to get a more reliable stack trace than the kernel dump. Looks > like a bug in some or another sysctl handler -- a stack trace from DDB may > be sufficient to debug it without a working core. Unfortunately no. It is a notebook without serial ports. It has a IEE1394 Port which could be used with DDB but I don't have a second box with Firewire. I also have a new kernel dump which shows gkrellm as current process. Can it still be a bug in sysctl? current process. Can it still be a bug in sysctl? -- Lars Engels E-Mail: lars.engels_at_0x20.net
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:38:57 UTC