Amaury Forgeot d'Arc [EMAIL PROTECTED] added the comment:
I reproduced the problem on windows, and it is indeed a problem with the
print statement, when the write() method reassigns sys.stdout: the
code calls PyFile_WriteString(), then PyFile_SoftSpace on the same
object, which has been freed in
Brodie Rao [EMAIL PROTECTED] added the comment:
Thanks. The patch fixes the crash for me on Python 2.5.2 and 2.6b1 on OS X
and Python 2.4.5 on Debian and Ubuntu.
___
Python tracker [EMAIL PROTECTED]
http://bugs.python.org/issue3242
Amaury Forgeot d'Arc [EMAIL PROTECTED] added the comment:
Corrected as r64633 (trunk) and r64639 (release25-maint). version 3.0 is
not affected, and there won't be any more 2.4 release.
Thanks for the report!
--
resolution: - fixed
status: open - closed
New submission from Brodie Rao [EMAIL PROTECTED]:
Running the attached script - which reassigns sys.stdout to an object
that proxies sys.stdout, and eventually reassigns it back to the
original object - using Apple's distribution of Python 2.5.1 on an x86
machine, I get the following crash:
Brodie Rao [EMAIL PROTECTED] added the comment:
Actually, this seems to be a hardware issue, despite the consistency
between runs and the duplication on another machine. I think you can
ignore/close this bug. Sorry for the noise.
___
Python tracker [EMAIL
Changes by Georg Brandl [EMAIL PROTECTED]:
--
resolution: - invalid
status: open - closed
___
Python tracker [EMAIL PROTECTED]
http://bugs.python.org/issue3242
___
___
Brodie Rao [EMAIL PROTECTED] added the comment:
Actually, I've tested this script on another Debian x86 machine and two
Ubuntu x86 machines, all which exhibit the exact same crash with their
Python 2.4 distributions. I don't think it's a hardware issue, I think
there's a legitimate issue
Benjamin Peterson [EMAIL PROTECTED] added the comment:
Can you try on later versions of Python. 2.4 is no longer supported.
--
nosy: +benjamin.peterson
resolution: invalid -
status: closed - open
___
Python tracker [EMAIL PROTECTED]
Brodie Rao [EMAIL PROTECTED] added the comment:
Using Python 2.5.2 from python.org on Mac OS X 10.5, I get the same
error:
Program received signal EXC_BAD_ACCESS, Could not access memory.
Reason: 13 at address: 0xad40
0x0052ed30 in ?? ()
(gdb) bt
#0 0x0052ed30 in ?? ()
#1 0x0002ad41 in
Brodie Rao [EMAIL PROTECTED] added the comment:
Running with Python 2.5.2 with guard malloc on OS X 10.5 produces a
similar crash to that of Python 2.4 on Linux:
(gdb) set env DYLD_INSERT_LIBRARIES /usr/lib/libgmalloc.dylib
(gdb) run ~/Documents/Code/py-crash/crash5.py
Starting program:
10 matches
Mail list logo