Xavier de Gaye added the comment:
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
Continuing.
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;
(gdb)
966 if (!PyArg_ParseTuple(args, "|i:_sigsegv", &release_gil))
(gdb)
969 if (release_gil) {
(gdb)
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();
(gdb)
958 raise(SIGSEGV);
(gdb)
Program received signal SIGSEGV, Segmentation fault.
0xb76ec126 in ?? ()
(gdb) c
Continuing.
----------
_______________________________________
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/issue26934>
_______________________________________
_______________________________________________
Python-bugs-list mailing list
Unsubscribe:
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
