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 xdegaye
Recipients Alex.Willmer, terry.reedy, vstinner, xdegaye
Date 2016-05-07.07:28:27
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
The gdb backtrace of running interactively 'faulthandler._sigsegv()'. After the SIGSEGV and the last gdb 'continue', python is still alive with a '>>>' prompt and ready for the next user input:

(gdb) b faulthandler_sigsegv
Breakpoint 1 at 0xb752159f: file /home/xavier/src/packages/android/cpython/Modules/faulthandler.c, line 964.
(gdb) c

Breakpoint 1, faulthandler_sigsegv (self=self@entry=<module at remote 0xb6d85cf4>, 
    args=args@entry=()) at /home/xavier/src/packages/android/cpython/Modules/faulthandler.c:964
964     {
(gdb) next
965         int release_gil = 0;
966         if (!PyArg_ParseTuple(args, "|i:_sigsegv", &release_gil))
969         if (release_gil) {
974             faulthandler_raise_sigsegv();
(gdb) step
faulthandler_raise_sigsegv ()
    at /home/xavier/src/packages/android/cpython/Modules/faulthandler.c:941
941     {
(gdb) next
942         faulthandler_suppress_crash_report();
958         raise(SIGSEGV);

Program received signal SIGSEGV, Segmentation fault.
0xb76ec126 in ?? ()
(gdb) c
Date User Action Args
2016-05-07 07:28:28xdegayesetrecipients: + xdegaye, terry.reedy, vstinner, Alex.Willmer
2016-05-07 07:28:28xdegayesetmessageid: <>
2016-05-07 07:28:28xdegayelinkissue26934 messages
2016-05-07 07:28:27xdegayecreate