Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://mail.python.org/pipermail/python-dev/2008-December/084393.html below:

[Python-Dev] Trap SIGSEGV and SIGFPE

• Previous message: [Python-Dev] Trap SIGSEGV and SIGFPE
• Next message: [Python-Dev] The endless GIL debate: why not remove thread support instead?
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

On Dec 11, 2008, at 3:05 PM, Martin v. Löwis wrote:
> If it is actually possible to print a stack trace, that could be  
> useful indeed. I'm then skeptical that this is possible in the  
> general case (i.e. displaying the full C stack), but displaying  
> (parts of) the Python stack might be possible. I think it should  
> still proceed to dump core, so that you can then inspect the core  
> with a proper debugger.


+1. Victor, any interest in attempting to retool your patch in this  
direction?

--
Ivan Krstić <krstic at solarsail.hcs.harvard.edu> | http://radian.org

• Previous message: [Python-Dev] Trap SIGSEGV and SIGFPE
• Next message: [Python-Dev] The endless GIL debate: why not remove thread support instead?
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

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