On Wed, Oct 20, 2004 at 12:13:46AM +0100, Chris Hedley wrote: > On Tue, 19 Oct 2004, Kris Kennaway wrote: > >On Tue, Oct 19, 2004 at 05:06:46PM +0100, Chris Hedley wrote: > >>>Unfortunately this doesn't seem to be useful - you should try to > >>>obtain a debugging traceback. > >> > >>That can be arranged. Just pretend for a moment that I'm really dense and > >>remind me how to go about creating one. ;) > > > >See the kernel debugging chapter in the developer's handbook. > > Hmm, that's what I already did. The only exception was having to use > "kgdb" instead of "gdb -k" (the latter complained that it didn't > understand "-k" which is odd, as it used to work). I was a bit surprised > that it didn't print the syslog buffer when I started it, too. If you don't use the kernel.debug, you won't get the debugging symbols. Kris
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:38:18 UTC