[issue4313] IDLE segfault at exit

2008-11-17 Thread Hirokazu Yamamoto
Hirokazu Yamamoto <[EMAIL PROTECTED]> added the comment: Fixed in r67256. I heard last RC will be released at this Wed, I think segfault is not good for it. -- resolution: -> fixed status: open -> closed ___ Python tracker <[EMAIL PROTECTED]>

[issue4313] IDLE segfault at exit

2008-11-14 Thread Hirokazu Yamamoto
Changes by Hirokazu Yamamoto <[EMAIL PROTECTED]>: -- nosy: +kbk ___ Python tracker <[EMAIL PROTECTED]> ___ ___ Python-bugs-list mailing

[issue4313] IDLE segfault at exit

2008-11-14 Thread Hirokazu Yamamoto
Hirokazu Yamamoto <[EMAIL PROTECTED]> added the comment: Sorry, I cannot reproduce the bug described in issue1028, so it's difficult for me. ___ Python tracker <[EMAIL PROTECTED]> ___ _

[issue4313] IDLE segfault at exit

2008-11-14 Thread STINNER Victor
STINNER Victor <[EMAIL PROTECTED]> added the comment: > Can I revert r57540 and reopen issue1028? Would it be possible to revert and fix the issue in the same commit? :-) ___ Python tracker <[EMAIL PROTECTED]> _

[issue4313] IDLE segfault at exit

2008-11-14 Thread Hirokazu Yamamoto
Hirokazu Yamamoto <[EMAIL PROTECTED]> added the comment: Can I revert r57540 and reopen issue1028? ___ Python tracker <[EMAIL PROTECTED]> ___ ___

[issue4313] IDLE segfault at exit

2008-11-14 Thread Hirokazu Yamamoto
Changes by Hirokazu Yamamoto <[EMAIL PROTECTED]>: Added file: http://bugs.python.org/file12007/idle_crash_2.py ___ Python tracker <[EMAIL PROTECTED]> ___ __

[issue4313] IDLE segfault at exit

2008-11-14 Thread Hirokazu Yamamoto
Hirokazu Yamamoto <[EMAIL PROTECTED]> added the comment: After long random investigation, I found idle_crash_1.py can reproduce the crash. And I noticed in idle_crash_2.py WidgetRedirector#dispatch, last element of args cannot be printed. Here is result. 10 0 -foreground 1 black 2 -selectforegro

[issue4313] IDLE segfault at exit

2008-11-13 Thread STINNER Victor
STINNER Victor <[EMAIL PROTECTED]> added the comment: The bug looks to be specific to Python3 but may comes from Tk and not directly from tkinter module. I recompiled Tk with debug symbols to get a better backtrace: malformed bucket chain in Tcl_DeleteHashEntry Program received signal SIGABRT,

[issue4313] IDLE segfault at exit

2008-11-13 Thread STINNER Victor
STINNER Victor <[EMAIL PROTECTED]> added the comment: The crash occurs when I close a window if a file was open. I can reproduce the crash on Debian Sid, so it's not a problem of an old library version. ___ Python tracker <[EMAIL PROTECTED]>

[issue4313] IDLE segfault at exit

2008-11-13 Thread STINNER Victor
New submission from STINNER Victor <[EMAIL PROTECTED]>: With Python 3.0 trunk on Ubuntu Gutsy, IDLE crashs at exit. gdb trace: Program received signal SIGSEGV, Segmentation fault. [Switching to Thread -1210763072 (LWP 9441)] 0xb79ac133 in Tk_Free3DBorder () from /usr/lib/libtk8.4.so.0 (gdb) wher