Menu
▾
▴
[Tcl-bugs] [ tktoolkit-Bugs-3341056 ] Usage of recreated ttk::checkbutton causes crash
|
From: SourceForge.net <no...@so...> - 2011-06-29 19:40:44
|
Bugs item #3341056, was opened at 2011-06-28 08:15 Message generated for change (Comment added) made by jenglish You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=112997&aid=3341056&group_id=12997 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: 88. Themed Tk Group: current: 8.5.10 Status: Open Resolution: None Priority: 9 Private: No Submitted By: Mihai Militaru (mihai_militaru) Assigned to: Don Porter (dgp) Summary: Usage of recreated ttk::checkbutton causes crash Initial Comment: - Since version 8.5.10 of Tcl and Tk only, it's not happening in 8.5.9. Not tested in other versions. Reproduced on Linux and a Virtualbox Windows installation. - The issue: if a ttk::checkbutton is destroyed and recreated - meaning another checkbutton with the same path is created - , activating the button causes a crash. The problem seems to be the widget's variable, if the widget's <Destroy> event is bound to unset its variable, the crash doesn't occur. - To reproduce: in case the description is not sufficient to reproduce from scratch, run the attached Tcl script with tclsh or wish, then press the button labeled "Button" for two times, then press the checkbutton labeled "Enabled ". - Operating system: Arch Linux 64bit, kernel version 2.6.39.1. - Tcl built with: ./configure --prefix=/usr --mandir=/usr/share/man --enable-threads --enable-64bit (--enable-symbols) - Tk built with: ./configure --prefix=/usr --mandir=/usr/share/man --enable-threads --enable-64bit (--enable-symbols) - The Valgrind output after the error: ==10686== Invalid read of size 8 ==10686== at 0x4ED55A1: Tcl_GetString (tclObj.c:1579) ==10686== by 0x6D92C98: CheckbuttonVariableChanged (ttkButton.c:450) ==10686== by 0x6DAA9F5: VarTraceProc (ttkTrace.c:69) ==10686== by 0x4EF584C: TclCallVarTraces (tclTrace.c:2639) ==10686== by 0x4EFD45C: TclPtrSetVar (tclVar.c:1904) ==10686== by 0x4EFF672: Tcl_ObjSetVar2 (tclVar.c:1718) ==10686== by 0x6D92A35: CheckbuttonInvokeCommand (ttkButton.c:543) ==10686== by 0x6DAA782: Ttk_InvokeEnsemble (ttkTheme.c:1679) ==10686== by 0x6DB0A2F: WidgetInstanceObjCmd (ttkWidget.c:161) ==10686== by 0x4E5F137: TclEvalObjvInternal (tclBasic.c:3699) ==10686== by 0x4EA1EB1: TclExecuteByteCode (tclExecute.c:2416) ==10686== by 0x4EA930F: TclCompEvalObj (tclExecute.c:1538) ==10686== Address 0x8 is not stack'd, malloc'd or (recently) free'd ==10686== ==10686== ==10686== Process terminating with default action of signal 11 (SIGSEGV) ==10686== Access not within mapped region at address 0x8 ==10686== at 0x4ED55A1: Tcl_GetString (tclObj.c:1579) ==10686== by 0x6D92C98: CheckbuttonVariableChanged (ttkButton.c:450) ==10686== by 0x6DAA9F5: VarTraceProc (ttkTrace.c:69) ==10686== by 0x4EF584C: TclCallVarTraces (tclTrace.c:2639) ==10686== by 0x4EFD45C: TclPtrSetVar (tclVar.c:1904) ==10686== by 0x4EFF672: Tcl_ObjSetVar2 (tclVar.c:1718) ==10686== by 0x6D92A35: CheckbuttonInvokeCommand (ttkButton.c:543) ==10686== by 0x6DAA782: Ttk_InvokeEnsemble (ttkTheme.c:1679) ==10686== by 0x6DB0A2F: WidgetInstanceObjCmd (ttkWidget.c:161) ==10686== by 0x4E5F137: TclEvalObjvInternal (tclBasic.c:3699) ==10686== by 0x4EA1EB1: TclExecuteByteCode (tclExecute.c:2416) ==10686== by 0x4EA930F: TclCompEvalObj (tclExecute.c:1538) ==10686== If you believe this happened as a result of a stack ==10686== overflow in your program's main thread (unlikely but ==10686== possible), you can try to increase the size of the ==10686== main thread stack using the --main-stacksize= flag. ==10686== The main thread stack size used in this run was 8388608. ==10686== ==10686== HEAP SUMMARY: ==10686== in use at exit: 2,977,557 bytes in 2,224 blocks ==10686== total heap usage: 15,288 allocs, 13,064 frees, 6,539,778 bytes allocated ==10686== ==10686== LEAK SUMMARY: ==10686== definitely lost: 1,280 bytes in 2 blocks ==10686== indirectly lost: 4,688 bytes in 146 blocks ==10686== possibly lost: 2,138,713 bytes in 134 blocks ==10686== still reachable: 832,876 bytes in 1,942 blocks ==10686== suppressed: 0 bytes in 0 blocks ==10686== Rerun with --leak-check=full to see details of leaked memory ==10686== ==10686== For counts of detected and suppressed errors, rerun with: -v ==10686== ERROR SUMMARY: 3327 errors from 26 contexts (suppressed: 46 from 10) Killed ---------------------------------------------------------------------- Comment By: Joe English (jenglish) Date: 2011-06-29 12:40 Message: Possible clue: problem does not manifest if [ttk::checkbutton] constructor is called directly from the % prompt; it seems to only occur if called from within a procedure body. Adding the missing "-variable" option seems to have no effect on whether this bug triggers (I thought at first this might be due to the ill-advised DWIM logic that automagically sets the checkbuttons -variable to the widget path name if not specified, but that apppears not to be the case.) ---------------------------------------------------------------------- Comment By: Joe English (jenglish) Date: 2011-06-29 12:20 Message: I am inclined to blame the fix for #3062331; dgp? ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=112997&aid=3341056&group_id=12997 |