[Python-Dev] Segmentation fault on 3.4 with --pydebug (original) (raw)
a.cavallo at cavallinux.eu a.cavallo at cavallinux.eu
Thu May 30 13:53:19 CEST 2013
- Previous message: [Python-Dev] Segmentation fault on 3.4 with --pydebug
- Next message: [Python-Dev] Segmentation fault on 3.4 with --pydebug
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
What's the stack trace?
$> gdb --args ./python.exe -Wd -m test.regrtest test_exceptions
and once in gdb: gdb> bt
That should point on where it happened. I hope this help
On 2013-05-30 13:08, Łukasz Langa wrote:
This happens after Benjamin's changes in 83937. Anybody else seeing this?
Intel i5 2.4 GHz, Mac OS X 10.8.3, clang $ hg up default $ make distclean $ MACOSXDEPLOYMENTTARGET=10.8 ./configure --with-pydebug $ make $ ./python.exe -Wd -m test.regrtest testexceptions [1/1] testexceptions Fatal Python error: Segmentation fault Current thread 0x00007fff74254180: File "/Users/ambv/Documents/Projekty/Python/cpython/py34/Lib/test/testexceptions.py", line 453 in f File "/Users/ambv/Documents/Projekty/Python/cpython/py34/Lib/test/testexceptions.py", line 453 in f File "/Users/ambv/Documents/Projekty/Python/cpython/py34/Lib/test/testexceptions.py", line 453 in f ... (repeated a 100 times) Command terminated abnormally. Everything runs fine without --with-pydebug (or before 83937 with --with-pydebug).
- Previous message: [Python-Dev] Segmentation fault on 3.4 with --pydebug
- Next message: [Python-Dev] Segmentation fault on 3.4 with --pydebug
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]