[issue17833] test_gdb broken PPC64 Linux

Changes by Ezio Melotti : -- Removed message: http://bugs.python.org/msg188621 ___ Python tracker ___ ___ Python-bugs-list mailing lis

[issue17833] test_gdb broken PPC64 Linux

Roundup Robot added the comment: New changeset 63f2941477d3 by Ezio Melotti in branch '2.7': #17833: add debug output to investigate buildbot failure. http://hg.python.org/cpython/rev/63f2941477d3 -- ___ Python tracker

[issue17833] test_gdb broken PPC64 Linux

Changes by Dave Malcolm : -- resolution: -> fixed stage: commit review -> committed/rejected status: open -> closed ___ Python tracker ___ __

[issue17833] test_gdb broken PPC64 Linux

Roundup Robot added the comment: New changeset f4a6b731905a by David Malcolm in branch '3.3': #17833: fix test_gdb failures seen on PPC64 Linux in test_threads (test.test_gdb.PyBtTests) http://hg.python.org/cpython/rev/f4a6b731905a New changeset 6d971b172389 by David Malcolm in branch 'default'

[issue17833] test_gdb broken PPC64 Linux

Changes by Antoine Pitrou : -- assignee: -> dmalcolm stage: -> commit review type: -> behavior versions: +Python 3.3 ___ Python tracker ___ ___

[issue17833] test_gdb broken PPC64 Linux

David Edelsohn added the comment: Thanks for explaining the issue with GLibc symbols. The Python test definitely should not fail if debugging symbols are installed. The "dot" symbols should no longer occur with modern PowerLinux installations. They were a carry-over from the AIX ABI on which

[issue17833] test_gdb broken PPC64 Linux

Siddhesh Poyarekar added the comment: It's not a change in glibc. __pthread_cond_timedwait is the internal function name while pthread_cond_timedwait is the exported alias. You're seeing __pthread_cond_timedwait here because either your glibc installation has debug symbols or you have debug

[issue17833] test_gdb broken PPC64 Linux

David Edelsohn added the comment: __pthread_cond_timedwait with underscore may be a general GLibc change. The patch fixes the failure. -- ___ Python tracker ___

[issue17833] test_gdb broken PPC64 Linux

Dave Malcolm added the comment: Can you try this candidate fix? -- Added file: http://bugs.python.org/file30007/possible-fix.patch ___ Python tracker ___

[issue17833] test_gdb broken PPC64 Linux

Dave Malcolm added the comment: Looking at test_gdb.out, the issue is that the threads waiting for the GIL have e.g. this at the top of their backtrace: Thread 2 (Thread 0x3fffb14af200 (LWP 37119)): #0 0x008075181ea8 in __pthread_cond_timedwait (cond=0x103ea140 , mutex=0x103ea170 , abstim

[issue17833] test_gdb broken PPC64 Linux

Changes by David Edelsohn : Added file: http://bugs.python.org/file30006/test_gdb.out ___ Python tracker ___ ___ Python-bugs-list mailing list

[issue17833] test_gdb broken PPC64 Linux

Dave Malcolm added the comment: Thanks. I can't see from that output what's going wrong. Can you apply the following patch, which (I hope) will print more detailed info where the failure happens. -- keywords: +patch Added file: http://bugs.python.org/file30005/find-more-information.pa

[issue17833] test_gdb broken PPC64 Linux

David Edelsohn added the comment: Unoptimized debug build (configured using --with-pydebug). Buildbot test failure running on gcc110 in GCC Compile Farm (running Fedora). gcc -pthread -c -Wno-unused-result -g -O0 -Wall -Wstrict-prototypes -m64 -- __

[issue17833] test_gdb broken PPC64 Linux

Dave Malcolm added the comment: Is this an optimized or a debug build? (aka --with-pydebug) What are the optimization flags passed to the C compiler? -- nosy: +dmalcolm ___ Python tracker

[issue17833] test_gdb broken PPC64 Linux

New submission from David Edelsohn: Verify that "py-bt" indicates threads that are waiting for the GIL ... FAIL FAIL: test_threads (test.test_gdb.PyBtTests) Verify that "py-bt" indicates threads that are waiting for the GIL -- T