Mike Klaas wrote:
On 10/18/06, Tim Peters [EMAIL PROTECTED] wrote:
[...]
Shouldn't the thread state generally be the same anyway? (I seem to
recall some gloomy warning against resuming generators in separate
threads).
Is this an indication that generators aren't thread-safe?
regards
Steve
[http://sourceforge.net/tracker/index.php?func=detailaid=1579370group_id=5470atid=105470]
Hello,
I'm managed to provoke a segfault in python2.5 (occasionally it just a
invalid argument to internal function error). I've posted a
traceback and a general idea of what the code consists of in the
Mike Klaas [EMAIL PROTECTED] writes:
[http://sourceforge.net/tracker/index.php?func=detailaid=1579370group_id=5470atid=105470]
Hello,
I'm managed to provoke a segfault in python2.5 (occasionally it just a
invalid argument to internal function error). I've posted a
traceback and a general
On 18-Oct-2006, at 22:08 , Michael Hudson wrote:
Unfortunately, I've been attempting for hours to
reduce the problem to a completely self-contained script, but it is
resisting my efforts due to timing problems.
Has anyone ever tried to use helgrind (the valgrind module, not the
heavy metal
On 10/18/06, Michael Hudson [EMAIL PROTECTED] wrote:
Mike Klaas [EMAIL PROTECTED] writes:
I've been reading the bug report with interest, but unless I can
reproduce it it's mighty hard for me to debug, as I'm sure you know.
Indeed.
Unfortunately, I've been attempting for hours to
reduce
[Michael Hudson]
I've been reading the bug report with interest, but unless I can
reproduce it it's mighty hard for me to debug, as I'm sure you know.
[Mike Klaas]
Indeed.
Note that I just attached a much simpler pure-Python script that fails
very quickly, on Windows, using a debug build.
On 10/18/06, Tim Peters [EMAIL PROTECTED] wrote:
[Mike Klaas]
Indeed.
Note that I just attached a much simpler pure-Python script that fails
very quickly, on Windows, using a debug build. Read the new comment
to learn why both Windows and debug build are essential to it
failing reliably
