[issue12468] longjmp causes uninitialized stack frame
Charles-François Natali
report at bugs.python.org
Sat Jul 2 12:16:19 CEST 2011
Charles-François Natali <neologix at free.fr> 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)[0x7f2415de60d3]
/usr/lib/libcurl-gnutls.so.4(+0xbb45)[0x7f241528bb45]
The longjmp is in libcurl.
Closing as invalid.
----------
resolution: -> invalid
stage: -> committed/rejected
status: open -> closed
_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue12468>
_______________________________________
More information about the Python-bugs-list
mailing list