[issue12468] longjmp causes uninitialized stack frame

Charles-François Natali added the comment: And the backtrace leaves no doubt: === Backtrace: = /lib/x86_64-linux-gnu/libc.so.6(__fortify_fail+0x37)[0x7f2415de61d7] /lib/x86_64-linux-gnu/libc.so.6(+0xfe169)[0x7f2415de6169] /lib/x86_64-linux-gnu/libc.so.6(__longjmp_chk+0x33)[0x7f2415de

[issue12468] longjmp causes uninitialized stack frame

Charles-François Natali added the comment: Digging a little deeper: - in ./Modules/fpectlmodule.c, the longjmp() is actually not used at all (dead code) - in Modules/readline.c, the jmp_buf is correctly initialized (well, there's a tiny race condition because SIGINT handler is installed before

[issue12468] longjmp causes uninitialized stack frame

Charles-François Natali added the comment: longjmp() is used in only two places: ./Modules/fpectlmodule.c:longjmp(PyFPE_jbuf, 1); ./Modules/readline.c:longjmp(jbuf, 1); Both use it to jump out of a signal handler, which can lead to undefined behaviour (see https://www.securecodin

[issue12468] longjmp causes uninitialized stack frame

Changes by Stefan Krah : -- nosy: +skrah ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org

[issue12468] longjmp causes uninitialized stack frame

Eric V. Smith added the comment: Do you have a python code snippet which triggers this? -- nosy: +eric.smith ___ Python tracker ___ _

[issue12468] longjmp causes uninitialized stack frame

New submission from Kiril Mikos : *** longjmp causes uninitialized stack frame ***: /usr/bin/python2.7 terminated === Backtrace: = /lib/x86_64-linux-gnu/libc.so.6(__fortify_fail+0x37)[0x7f2415de61d7] /lib/x86_64-linux-gnu/libc.so.6(+0xfe169)[0x7f2415de6169] /lib/x86_64-linux-gnu/libc.