>Our custom C++ tag is dying with a sig11
Count your blessings: sig11 is a form of catastrophic
failure. Subtle, non-deterministic bugs can make
you nuts, but (reproducible) catastrophic failures
are a gift; they just keep failing obligingly in the
same place for the same reasons as you triangulate.
Think of it as a game of Marco-Polo, while the
non-deterministic bugs are more like dating...
Let me assure you that I don't know sh*t about
Cold Fusion, Sablotron, Apache or whatever, but I
know a bit about systems-software and debugging.
Some preliminary questions:
- Is the failing module part of some nasty-huge
whole or soem smaller thing that gets launched
in response to some input?
- Can you substitute some other program for the
failing module?
- Can you capture whatever data are being fed
to the failing module?
- Can you pause the system immediately prior to
it launching the failing module?
- Can you run the failing module under GDB?
- Have you got any recreational drugs?
*****************************************************************
To unsubscribe from this list, send mail to [EMAIL PROTECTED]
with the text 'unsubscribe gnhlug' in the message body.
*****************************************************************
