Segmentation fault on 3.4 with --pydebug
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 $ MACOSX_DEPLOYMENT_TARGET=10.8 ./configure --with-pydebug $ make $ ./python.exe -Wd -m test.regrtest test_exceptions [1/1] test_exceptions Fatal Python error: Segmentation fault Current thread 0x00007fff74254180: File "/Users/ambv/Documents/Projekty/Python/cpython/py34/Lib/test/test_exceptions.py", line 453 in f File "/Users/ambv/Documents/Projekty/Python/cpython/py34/Lib/test/test_exceptions.py", line 453 in f File "/Users/ambv/Documents/Projekty/Python/cpython/py34/Lib/test/test_exceptions.py", line 453 in f ... (repeated a 100 times) Command terminated abnormally. Everything runs fine without --with-pydebug (or before 83937 with --with-pydebug). -- Best regards, Łukasz Langa WWW: http://lukasz.langa.pl/ Twitter: @llanga IRC: ambv on #python-dev
No for me: $ ./python -Wd -m test.regrtest test_exceptions [1/1] test_exceptions 1 test OK. $ uname -a Linux 3.2.0-32-generic #51-Ubuntu SMP Wed Sep 26 21:32:50 UTC 2012 i686 i686 i386 GNU/Linux Please look at issue18075 2013/5/30 Łukasz Langa <lukasz@langa.pl>:
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 $ MACOSX_DEPLOYMENT_TARGET=10.8 ./configure --with-pydebug $ make $ ./python.exe -Wd -m test.regrtest test_exceptions [1/1] test_exceptions Fatal Python error: Segmentation fault
Current thread 0x00007fff74254180: File "/Users/ambv/Documents/Projekty/Python/cpython/py34/Lib/test/test_exceptions.py", line 453 in f File "/Users/ambv/Documents/Projekty/Python/cpython/py34/Lib/test/test_exceptions.py", line 453 in f File "/Users/ambv/Documents/Projekty/Python/cpython/py34/Lib/test/test_exceptions.py", line 453 in f ... (repeated a 100 times) Command terminated abnormally.
Everything runs fine without --with-pydebug (or before 83937 with --with-pydebug).
-- Best regards, Łukasz Langa
WWW: http://lukasz.langa.pl/ Twitter: @llanga IRC: ambv on #python-dev
_______________________________________________ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/dmi.baranov%40gmail.com
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 $ MACOSX_DEPLOYMENT_TARGET=10.8 ./configure --with-pydebug
$ make $ ./python.exe -Wd -m test.regrtest test_exceptions
[1/1] test_exceptions Fatal Python error: Segmentation fault
Current thread 0x00007fff74254180: File
"/Users/ambv/Documents/Projekty/Python/cpython/py34/Lib/test/test_exceptions.py", line 453 in f File
"/Users/ambv/Documents/Projekty/Python/cpython/py34/Lib/test/test_exceptions.py", line 453 in f File
"/Users/ambv/Documents/Projekty/Python/cpython/py34/Lib/test/test_exceptions.py", line 453 in f ... (repeated a 100 times) Command terminated abnormally.
Everything runs fine without --with-pydebug (or before 83937 with --with-pydebug).
On 30 May, 2013, at 13:08, Łukasz Langa <lukasz@langa.pl> 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 $ MACOSX_DEPLOYMENT_TARGET=10.8 ./configure --with-pydebug $ make $ ./python.exe -Wd -m test.regrtest test_exceptions [1/1] test_exceptions Fatal Python error: Segmentation fault
Current thread 0x00007fff74254180: File "/Users/ambv/Documents/Projekty/Python/cpython/py34/Lib/test/test_exceptions.py", line 453 in f File "/Users/ambv/Documents/Projekty/Python/cpython/py34/Lib/test/test_exceptions.py", line 453 in f File "/Users/ambv/Documents/Projekty/Python/cpython/py34/Lib/test/test_exceptions.py", line 453 in f ... (repeated a 100 times) Command terminated abnormally.
Everything runs fine without --with-pydebug (or before 83937 with --with-pydebug).
Issue #18075 contains a patch. I probably won't have time to commit until sunday, but feel free to apply the patch yourself :-) Ronald
On 30 maj 2013, at 14:45, Ronald Oussoren <ronaldoussoren@mac.com> wrote:
Issue #18075 contains a patch. I probably won't have time to commit until sunday, but feel free to apply the patch yourself :-)
I did just that. Fixed, thanks! -- Best regards, Łukasz Langa WWW: http://lukasz.langa.pl/ Twitter: @llanga IRC: ambv on #python-dev
2013/5/30 Łukasz Langa <lukasz@langa.pl>:
This happens after Benjamin's changes in 83937. Anybody else seeing this?
Remember you need the hash to fully identify hg changesets. :)
Intel i5 2.4 GHz, Mac OS X 10.8.3, clang
$ hg up default $ make distclean $ MACOSX_DEPLOYMENT_TARGET=10.8 ./configure --with-pydebug $ make $ ./python.exe -Wd -m test.regrtest test_exceptions [1/1] test_exceptions Fatal Python error: Segmentation fault
As noted, it's infinite recursion. Without optimization I've noticed clang is very inefficient with respect to stack space, so for example, each PyEval_FrameEx frame is 1/2 KB. -- Regards, Benjamin
participants (5)
-
a.cavallo＠cavallinux.eu -
Benjamin Peterson -
Dmitriy Baranov -
Ronald Oussoren -
Łukasz Langa