[issue3685] Crash while compiling Python 3000 in OpenBSD 4.4

Barry A. Warsaw <[EMAIL PROTECTED]> added the comment: r66948 -- nosy: +barry resolution: -> accepted status: open -> closed ___ Python tracker <[EMAIL PROTECTED]> ___ ___

[issue3685] Crash while compiling Python 3000 in OpenBSD 4.4

Changes by Barry A. Warsaw <[EMAIL PROTECTED]>: -- priority: deferred blocker -> release blocker ___ Python tracker <[EMAIL PROTECTED]> ___

[issue3685] Crash while compiling Python 3000 in OpenBSD 4.4

Henry Precheur <[EMAIL PROTECTED]> added the comment: I just tested the patch and it fixes the problem. ___ Python tracker <[EMAIL PROTECTED]> ___ __

[issue3685] Crash while compiling Python 3000 in OpenBSD 4.4

Changes by Barry A. Warsaw <[EMAIL PROTECTED]>: -- priority: release blocker -> deferred blocker ___ Python tracker <[EMAIL PROTECTED]> ___

[issue3685] Crash while compiling Python 3000 in OpenBSD 4.4

Martin v. Löwis <[EMAIL PROTECTED]> added the comment: Is there any problem with always computing the end of the string as "s + wcslen(s)"? I feel that this is actually more readable than wcschr. Here is a patch that does that. It doesn't change PC/getpathp.c, since it's only used on Windows, wh

[issue3685] Crash while compiling Python 3000 in OpenBSD 4.4

Changes by Barry A. Warsaw <[EMAIL PROTECTED]>: -- priority: deferred blocker -> release blocker ___ Python tracker <[EMAIL PROTECTED]> ___

[issue3685] Crash while compiling Python 3000 in OpenBSD 4.4

Henry Precheur <[EMAIL PROTECTED]> added the comment: Here is a better patch which use the workaround only if wcschr is broken. I was able to build the python interpreter and to run regrtest.py with it (some tests fail but it is very likely to be bugs in the modules) Added file: http://bugs.pyt

[issue3685] Crash while compiling Python 3000 in OpenBSD 4.4

Changes by Benjamin Peterson <[EMAIL PROTECTED]>: -- priority: release blocker -> deferred blocker ___ Python tracker <[EMAIL PROTECTED]> ___ __

[issue3685] Crash while compiling Python 3000 in OpenBSD 4.4

Henry Precheur <[EMAIL PROTECTED]> added the comment: Looks like my other issue is unrelated. It is caused by a buggy mbstowcs. ___ Python tracker <[EMAIL PROTECTED]> ___ __

[issue3685] Crash while compiling Python 3000 in OpenBSD 4.4

Henry Precheur <[EMAIL PROTECTED]> added the comment: Indeed it looks like it is the source of the problem. I created a patch to fix it. But it looks like there is another problem, instead of crashing the Python interpreter goes into interactive mode instead of executing the 'setup.py' script .

[issue3685] Crash while compiling Python 3000 in OpenBSD 4.4

Hye-Shik Chang <[EMAIL PROTECTED]> added the comment: This problem is due to OpenBSD's libc bug. It's fixed 3 days ago. (http://www.openbsd.org/cgi- bin/cvsweb/src/lib/libc/string/wcschr.c#rev1.4) We can workaround by replacing use of wcschr(ws, L'\0') to ws + wcslen(ws). -- nosy: +hyes

[issue3685] Crash while compiling Python 3000 in OpenBSD 4.4

Changes by Antoine Pitrou <[EMAIL PROTECTED]>: -- components: +Interpreter Core priority: -> release blocker type: -> crash ___ Python tracker <[EMAIL PROTECTED]> ___ ___

[issue3685] Crash while compiling Python 3000 in OpenBSD 4.4

Henry Precheur <[EMAIL PROTECTED]> added the comment: I forgot to mention, I made to following modification to configure.in so I could compile Python 3000 on OpenBSD 4.4 --- configure.in(revision 66037) +++ configure.in(working copy) @@ -250,7 +250,7 @@ # On OpenBSD, select(2)

[issue3685] Crash while compiling Python 3000 in OpenBSD 4.4

New submission from Henry Precheur <[EMAIL PROTECTED]>: I tried to compile Python 3000 under OpenBSD and the compilation fails because of a 'MemoryError': Fatal Python error: can't create sys.path object : MemoryError() type: MemoryError refcount: 4 address : 0x20abfbd08 lost sys.stderr Abo