Include bus errors and aborts, as well as segmentation violations, as
authorguy <guy@f5534014-38df-0310-8fa8-9805f1628bb7>
Thu, 24 Aug 2000 23:33:09 +0000 (23:33 +0000)
committerguy <guy@f5534014-38df-0310-8fa8-9805f1628bb7>
Thu, 24 Aug 2000 23:33:09 +0000 (23:33 +0000)
commitf9fbba7725f8307649c74012694459ca4001c22a
tree195abec0eb5dd5f7aba37814730b663a39781606
parentb446ada7b2ac7170270cc997f9d6464f49738784
Include bus errors and aborts, as well as segmentation violations, as
examples of errors that generate core dumps, and suggest that a stack
trace from the debugger could be useful for *all* failures that produce
core dumps.

Note that the core dump file may be named "ethereal.core", and note that
"tethereal" rather than "ethereal" should be used in file names if it's
Tethereal that blew up.

git-svn-id: http://anonsvn.wireshark.org/wireshark/trunk@2368 f5534014-38df-0310-8fa8-9805f1628bb7
README