[ python-Bugs-995956 ] TclError with intel's hypertheading
SourceForge.net
noreply at sourceforge.net
Wed Apr 12 10:06:17 CEST 2006
Bugs item #995956, was opened at 2004-07-22 16:49
Message generated for change (Comment added) made by loewis
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=995956&group_id=5470
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: Tkinter
Group: Python 2.3
Status: Open
Resolution: None
Priority: 5
Submitted By: Tobias Haar (thaar)
>Assigned to: Nobody/Anonymous (nobody)
Summary: TclError with intel's hypertheading
Initial Comment:
If i use the "intel hyperthreading technologie", my
python application make a coredump with the output:
File "C:\PROGRA~2\PYTHON~2\lib\lib-tk\Tkinter.py",
line 472, in after
return self.tk.call('after', ms, name)
TclError: expected integer but got "9118984callit"
The test runs at the following system.
Microsoft windows 2000 5.00.2195 Service Pack 4
Intel Pentium 4 CPU 2.5 Ghz
522.988 KB RAM.
The error never occur, if i turn the hyperthreading in
the bios off.
I made the self test at 2 other pc with the same
hardware and configurations. The result was the same.
I made another test with a linux pc, a laptop with xp
and a laptop with win2000. All without hyperthreading.
The error has not occured.
I add the log file and the test as attachment.
----------------------------------------------------------------------
>Comment By: Martin v. Löwis (loewis)
Date: 2006-04-12 10:06
Message:
Logged In: YES
user_id=21627
I don't think I will do anything about this anytime soon, so
unassigning myself.
----------------------------------------------------------------------
Comment By: Terry J. Reedy (tjreedy)
Date: 2004-07-30 01:38
Message:
Logged In: YES
user_id=593130
I believe TclError means that the error came from the
embedded Tcl interpreter. If so, and if the Pytyhon call
ultimately feeds appropriate data to Tcl, the problem comes
not from Python but one of Tcl, Win2000, or the chip, or the
relationship between them. If you are running current Python
with current Tcl, the best we could do is add a warning to
turn off Hyperthreading if strange errors occur, but I am not
sure where.
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=995956&group_id=5470
More information about the Python-bugs-list
mailing list