Re: How to provide useful debug info

Harald Schmalzbauer wrote: Bob Bishop wrote: See http://www.uk.freebsd.org/doc/en_US.ISO8859-1/books/developers-han dbook/kerneldebug.html, particularly 17.4 and 17.5 Thank you for that link, but that's far too complicated for me. I don't know any of these gdb commands, I can just

How to provide useful debug info

Hi all, I have currently at least 4 scenarios when my 5.1-release crashes on different hardware. So I built a kernel (GENERIC) with debugging symbols and DDB option. Now I'd like to provide usefull info about the following crashes: 1. booting from degraded RAID1 with HPT372 (machine crashes and

Re: How to provide useful debug info

Hi, Generally the minimum required information is /var/run/dmesg.boot and a stack backtrace at the crash. See http://www.uk.freebsd.org/doc/en_US.ISO8859-1/books/developers-handbook/kerneldebug.html, particularly 17.4 and 17.5 At 13:13 23/7/03, Harald Schmalzbauer wrote: Hi all, I have

RE: How to provide useful debug info

Bob Bishop wrote: Hi, Generally the minimum required information is /var/run/dmesg.boot and a stack backtrace at the crash. See http://www.uk.freebsd.org/doc/en_US.ISO8859-1/books/developers-han dbook/kerneldebug.html, particularly 17.4 and 17.5 Thank you for that link, but that's far