On Sunday, 1 August 1999 at 23:33:07 +0200, Andrzej Bialecki wrote:
> On Sat, 31 Jul 1999, Jeroen Ruigrok/Asmodai wrote:
>
>>
>> No, just options DDB.
>> This bt was obtained after doing gdb -k kernel.0 vmcore.0
>> I still have the DDB trace on paper which I can type in if needed/wanted.
>>
>>> What you do with the results depends a lot on what you find. On the
>>> whole, I wouldn't think it worth the pain of debugging without
>>> symbols.
>>
>> No it isn't...
>
> Another handful tricks of the trade:
>
> * if you still have exactly the same source tree and config file,
> recompile the kernel with -g to obtain the version with debugging symbols
bde has reported that the code may not be identical when compiling for
debugging. It should be, but for obscure reasons it doesn't quite
make it.
> * if you can't for the life of you get the crash dump to examine what went
> wrong, do remember of remote GDB option under DDB - that is, if you have
> another machine with the same sources and kenel. But if the problem is
> repeatable you can prepare it beforehand... Remote GDB works miracles
> then.
When it works. It's very temperamental.
Greg
--
See complete headers for address, home page and phone numbers
finger [EMAIL PROTECTED] for PGP public key
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
