This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author neologix
Recipients Vladimir.Ushakov, christian.heimes, neologix
Date 2012-10-12.21:19:27
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <CAH_1eM1APNaEHJ96+nMQ0BhRFb33U68oZY50TBgjHvuktDs_EQ@mail.gmail.com>
In-reply-to <1350064845.28.0.11889976216.issue16212@psf.upfronthosting.co.za>
Content
> I think, handling the signal would do.

You can't.
Handling a signal like SIGSEGV or SIGBUS in any other way that exiting
the process will result in an infinite loop (as soon as the signal
handler returns the faulty instruction will be re-executed). Well,
there are some higly non-portable ways to try to escape this (see
http://stackoverflow.com/questions/2663456/write-a-signal-handler-to-catch-sigsegv),
but it won't fly in our case.
You may want to have a look at the faulthandler module for "graceful"
shutdown, but nothing can't be done.
History
Date User Action Args
2012-10-12 21:19:28neologixsetrecipients: + neologix, christian.heimes, Vladimir.Ushakov
2012-10-12 21:19:28neologixlinkissue16212 messages
2012-10-12 21:19:27neologixcreate