[issue12588] test_capi.test_subinterps() failed on OpenBSD (powerpc)

Change by Irit Katriel : -- resolution: -> out of date stage: -> resolved status: open -> closed ___ Python tracker ___ ___ Python

[issue12588] test_capi.test_subinterps() failed on OpenBSD (powerpc)

Change by Mark Lawrence : -- nosy: -BreamoreBoy ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail

[issue12588] test_capi.test_subinterps() failed on OpenBSD (powerpc)

Landry Breuil added the comment: Seems something in between fixed it, because it works with 3.4.1. Can test 3.3 if needed. mikey:/usr/obj/tmpfs/ports/Python-3.4.1/Python-3.4.1/ $LD_LIBRARY_PATH=. ./Modules/_testembed --- Pass 0 --- interp 0xac003e00, thread state 0xb4380f80: id(modules) = 2813

[issue12588] test_capi.test_subinterps() failed on OpenBSD (powerpc)

Mark Lawrence added the comment: Is this test failure still relevant three years on? -- nosy: +BreamoreBoy status: pending -> open ___ Python tracker ___

[issue12588] test_capi.test_subinterps() failed on OpenBSD (powerpc)

Changes by Charles-François Natali : -- status: open -> pending ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue12588] test_capi.test_subinterps() failed on OpenBSD (powerpc)

Charles-François Natali added the comment: and Darwin). It would have been useful... """ interp 0x0, thread state 0x81855380: Program received signal SIGSEGV, Segmentation fault. """ Here, the interpreter state is NULL, and this shouldn't happen. It could be a bug linked to thread-local stora

[issue12588] test_capi.test_subinterps() failed on OpenBSD (powerpc)

rpointel added the comment: Hello, I just want to inform you that valgrind does not work on OpenBSD (only Linux and Darwin). Thanks for your help, Remi. -- ___ Python tracker __

[issue12588] test_capi.test_subinterps() failed on OpenBSD (powerpc)

Charles-François Natali added the comment: > Previous frame inner to this frame (corrupt stack?) Interesting. Could you post the result of: $ valgrind --tool=memcheck --suppressions=Misc/valgrind-python.supp Modules/_testembed after having un-commented the ADDRESS_IN_RANGE suppressions from

[issue12588] test_capi.test_subinterps() failed on OpenBSD (powerpc)

Landry Breuil added the comment: You get the same issue : [23:08] mikey:/usr/obj/ports/Python-3.2.1/Python-3.2.1/ $cp Modules/_testembed . [23:08] mikey:/usr/obj/ports/Python-3.2.1/Python-3.2.1/ $LD_LIBRARY_PATH=. gdb _testembed GNU gdb 6.3 Copyright 2004 Free Software F

[issue12588] test_capi.test_subinterps() failed on OpenBSD (powerpc)

Roumen Petrov added the comment: Hi Landry , what is result if you move _testembed to upper directory and run it with environment so that shared python library from upper to be loaded (LD_LIBRARY_PATH= )? -- nosy: +rpetrov ___ Python tracker <

[issue12588] test_capi.test_subinterps() failed on OpenBSD (powerpc)

Landry Breuil added the comment: (gdb) r Starting program: /usr/obj/ports/Python-3.2.1/Python-3.2.1/Modules/_testembed --- Pass 0 --- interp 0x90ae7300, thread state 0x87b48a00: id(modules) = 2363177552 interp 0x90ae7a40, thread state 0x87b48a80: id(modules) = 2243881408 interp 0x90ae7cc0, thre

[issue12588] test_capi.test_subinterps() failed on OpenBSD (powerpc)

Antoine Pitrou added the comment: test_subinterps merely runs ./Modules/_testembed, so perhaps you could launch it manually and see what it does? (chances are it crashes, then can you please post the backtrace using a debugger?) -- nosy: +pitrou __

[issue12588] test_capi.test_subinterps() failed on OpenBSD (powerpc)

New submission from rpointel : Hello, the test test_subinterps failed on OpenBSD on powerpc architecture. It works fine on amd64 and sparc64. (The test_pendingcalls_threaded has been skipped because it blocks on OpenBSD). Don't hesitate if you need more informations. Details: Re-running test 't