[Python-Dev] Trap SIGSEGV and SIGFPE

[Terry Reedy]

Benjamin Peterson wrote:
> On Wed, Dec 10, 2008 at 12:37 PM, Victor Stinner

>>> This will of course leave the program in an undefined state.  It is
>>> very likely to crash again, emit garbage, hang, or otherwise be
>>> useless.
>> Recover after a segfault is dangerous, but my first goal was to get the Python
>> backtrace instead just one line: "Segmentation fault". It helps a lot for
>> debug!
> 
> Exactly! That's why it doesn't belong in the Python core. We can't
> guarantee anything about its affects or encourage it.

Would it be safe to catch SIGSEGV, output a trace, and then exit?
IE, make the 'first goal' the only goal?