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 schmir
Recipients Rhamphoryncus, gvanrossum, schmir, tebeka
Date 2008-01-14.19:30:51
SpamBayes Score 0.0224642
Marked as misclassified No
Message-id <1200339053.35.0.539461294365.issue1215@psf.upfronthosting.co.za>
In-reply-to
Content
Those who want to legitimately catch SIGSEGV will end up with an
uninterruptible python process using 100 % CPU on a real segmentation fault.
But, then I can live with the current behaviour.
History
Date User Action Args
2008-01-14 19:30:53schmirsetspambayes_score: 0.0224642 -> 0.0224642
recipients: + schmir, gvanrossum, tebeka, Rhamphoryncus
2008-01-14 19:30:53schmirsetspambayes_score: 0.0224642 -> 0.0224642
messageid: <1200339053.35.0.539461294365.issue1215@psf.upfronthosting.co.za>
2008-01-14 19:30:52schmirlinkissue1215 messages
2008-01-14 19:30:52schmircreate