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?
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4