|
Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email hr@neohapsis.com |
From: Nick Holland (nick_at_holland-consulting.net)
Date: Tue Oct 01 2002 - 22:20:13 CDT
Bob DeBolt wrote:
>
> Greets
>
> I have looked at numerous docs and have not found how
> to capture a debug trace to file for transport to the mailing
> list. I have seen many who hand typed to another computer,
> seems there must be an easier way.
IF you can persuade it to crash while you had a serial console hooked
up, I suspect you would find the solutions obvious.
If not...grab the paper and pencil. (or another computer and text
editor...)
Don't expect much sympathy...
I've done plenty of typing ps and trace output into one computer from
another, while sitting on an old 2U switch on end.
It certainly motiviates one to have their ducks in order before
complaining about a crash. Is it really a software problem? Or did
your hardware go funny on you?
Tip: If you expect the thing to bomb, run the absolute minimum amount
of stuff. The ps and trace are shorter that way. 8-)
Of course, if you expect it to bomb...have the serial console going.
Why not just have it record the info to disk? Well, my suspicion is,
after something completely unexpected happens, do you really trust the
OS to politely write the relevant stuff to disk neatly and cleanly?
Nick.
-- http://www.holland-consulting.net
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]