[issue11327] Running test_time.py in python27 caused python to unexpectedly quit

2011-02-26 Thread Brett Cannon
Changes by Brett Cannon : -- resolution: -> out of date status: open -> closed ___ Python tracker ___ ___ Python-bugs-list mailing li

[issue11327] Running test_time.py in python27 caused python to unexpectedly quit

2011-02-26 Thread Charles-Francois Natali
Charles-Francois Natali added the comment: I updated my local svn checkout, and the code has been fixed recently: r87648 | alexander.belopolsky | 2011-01-02 15:48:22 -0500 (Sun, 02 Jan 2011) | 1 line Issue #8013: Fixed time.asctime segfault when OS's asctime fails p = asctime(&bu

[issue11327] Running test_time.py in python27 caused python to unexpectedly quit

2011-02-26 Thread Charles-Francois Natali
Charles-Francois Natali added the comment: > If it's broken, complain to Apple. Actually, I checked glibc's asctime, and it has the same behaviour. But the point is that asctime can return NULL. > That still doesn't explain the OP's crash on OS X 10.6.6. Yes it does. If asctime returns NULL,

[issue11327] Running test_time.py in python27 caused python to unexpectedly quit

2011-02-26 Thread Ned Deily
Ned Deily added the comment: If it's broken, complain to Apple. $ otool -L $(/opt/local/bin/python2.7 -c 'import time;print(time.__file__)') /opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/lib-dynload/time.so: /usr/lib/libSystem.B.dylib (compatibility version 1

[issue11327] Running test_time.py in python27 caused python to unexpectedly quit

2011-02-26 Thread Charles-Francois Natali
Charles-Francois Natali added the comment: This explains why you don't get a segfault: your libc is broken ;-) -- ___ Python tracker ___

[issue11327] Running test_time.py in python27 caused python to unexpectedly quit

2011-02-26 Thread Ned Deily
Ned Deily added the comment: $ /opt/local/bin/python2.7 Python 2.7.1 (r271:86832, Dec 31 2010, 11:59:23) [GCC 4.2.1 (Apple Inc. build 5664)] on darwin Type "help", "copyright", "credits" or "license" for more information. >>> import time >>> time.asctime((2011, 2, 26, -1, 0, 0, 0, 0, 0)) 'Mon F

[issue11327] Running test_time.py in python27 caused python to unexpectedly quit

2011-02-26 Thread Antoine Pitrou
Changes by Antoine Pitrou : -- nosy: +belopolsky ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.py

[issue11327] Running test_time.py in python27 caused python to unexpectedly quit

2011-02-26 Thread Charles-Francois Natali
Charles-Francois Natali added the comment: True with the following: import time time.asctime((2011, 2, 26, -1, 0, 0, 0, 0, 0)) You'll get a segfault. -- ___ Python tracker __

[issue11327] Running test_time.py in python27 caused python to unexpectedly quit

2011-02-26 Thread Ned Deily
Ned Deily added the comment: >From the path names in the trace you appear to have a MacPorts Python 2.7 >installed. For what it's worth, the standard library test_time works for me >on OS X 10.6.6 with a current MacPorts 2.7.1 as well as a python.org 2.7.1. >Exactly how did you try to run t

[issue11327] Running test_time.py in python27 caused python to unexpectedly quit

2011-02-26 Thread Charles-Francois Natali
Charles-Francois Natali added the comment: Exception Type: EXC_BAD_ACCESS (SIGSEGV) Exception Codes: KERN_INVALID_ADDRESS at 0x0018 Crashed Thread: 0 Dispatch queue: com.apple.main-thread Python crashes when dereferencing 0x0018, which is NULL + 24 This means that it

[issue11327] Running test_time.py in python27 caused python to unexpectedly quit

2011-02-25 Thread Anthony Long
New submission from Anthony Long : I ran python test_time.py and python immediately crashed. This is the trace from mac's error reporter: http://dpaste.de/Jsw7/ -- components: Tests messages: 129502 nosy: antlong priority: normal severity: normal status: open title: Running test_t