Re: how to interpret crash?
From: Daniel O'Connor (doconnor_at_gsoft.com.au)
Date: 05/28/04
- Previous message: David Magda: "Re: how to interpret crash?"
- In reply to: Robert Watson: "Re: how to interpret crash?"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
To: Robert Watson <rwatson@freebsd.org> Date: Thu, 27 May 2004 14:51:44 -1000
On Thu, 2004-05-27 at 13:55, Robert Watson wrote:
> I don't debate your basic point that on a stable system, you're least
> likely to find the symbols when you most need them, as the system will run
> fine for a long time and then run into some edge case, unusual hardware
> failure mode, or whatever, and given that it's been stable for years, you
> will find yourself with little debugging recourse. That's where tricks
> like using nm to track down the symbols, turning on dumps by default,
> compiling with the necessary DDB bits to generate a stack trace, etc, can
> come in quite handy.
I think turning on dumps by default is a good habit for sys admins to
get into :)
If the system dies and cores then you can rebuild your kernel with
debugging symbols and see where it died. At least that's _supposed_ to
work from what I've heard :)
-- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C
- application/pgp-signature attachment: This is a digitally signed message part
- Previous message: David Magda: "Re: how to interpret crash?"
- In reply to: Robert Watson: "Re: how to interpret crash?"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]