[issue34007] test_gdb fails in s390x SLES buildbots

Pablo Galindo Salgado added the comment: New changeset 963bcc8b71e4ab8c9ee9a91ed1300b6e39219821 by Pablo Galindo in branch '3.6': [3.6] bpo-34007: Skip traceback tests if the Program Counter is not available. (GH-9022) https://github.com/python/cpython/commit/963bcc8b71e4ab8c9ee9a91ed1300b6e

[issue34007] test_gdb fails in s390x SLES buildbots

Change by Pablo Galindo Salgado : -- pull_requests: +8490 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: htt

[issue34007] test_gdb fails in s390x SLES buildbots

miss-islington added the comment: New changeset 4da71814b327cb2ad47a01710360cd21ba636352 by Miss Islington (bot) in branch '3.7': bpo-34007: Skip traceback tests if the Program Counter is not available. (GH-9018) https://github.com/python/cpython/commit/4da71814b327cb2ad47a01710360cd21ba6363

[issue34007] test_gdb fails in s390x SLES buildbots

miss-islington added the comment: New changeset 5d594f3106aff6cea00234c88051427ae511cdd8 by Miss Islington (bot) in branch '2.7': bpo-34007: Skip traceback tests if the Program Counter is not available. (GH-9018) https://github.com/python/cpython/commit/5d594f3106aff6cea00234c88051427ae511cd

[issue34007] test_gdb fails in s390x SLES buildbots

Change by Pablo Galindo Salgado : -- stage: patch review -> resolved status: open -> closed ___ Python tracker ___ ___ Python-bugs-l

[issue34007] test_gdb fails in s390x SLES buildbots

Change by miss-islington : -- pull_requests: +8489 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://ma

[issue34007] test_gdb fails in s390x SLES buildbots

Change by miss-islington : -- pull_requests: +8488 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://ma

[issue34007] test_gdb fails in s390x SLES buildbots

Change by miss-islington : -- pull_requests: +8487 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://ma

[issue34007] test_gdb fails in s390x SLES buildbots

Pablo Galindo Salgado added the comment: New changeset f2ef51f8bec525b21e5290c8a029642795ed by Pablo Galindo in branch 'master': bpo-34007: Skip traceback tests if the Program Counter is not available. (GH-9018) https://github.com/python/cpython/commit/f2ef51f8bec525b21e5290c8a029642

[issue34007] test_gdb fails in s390x SLES buildbots

Change by Pablo Galindo Salgado : -- keywords: +patch pull_requests: +8486 stage: -> patch review ___ Python tracker ___ ___ Python

[issue34007] test_gdb fails in s390x SLES buildbots

Pablo Galindo Salgado added the comment: Interestingly, everything points to something special in the glibc version of the buildbot. Usually the end of the stack for threads is: (gdb) #22 0x77f82a9d in start_thread () from /usr/lib/libpthread.so.0 (gdb) #23 0x77d23a43 in clone

[issue34007] test_gdb fails in s390x SLES buildbots

Pablo Galindo Salgado added the comment: Walking the stack up one by one only triggers the "PC not saved" when the stack goes into libc: (gdb) break builtin_id Breakpoint 1 at 0x139403c: file Python/bltinmodule.c, line 1182. (gdb) r Starting program: /home/linux1/cpython/python tester.py Miss

[issue34007] test_gdb fails in s390x SLES buildbots

Pablo Galindo Salgado added the comment: I need to do some more experimenting because those symbols are not available on other systems with the test passing. Something is corrupting/not saving the program counter but I do not know what. -- ___ Pyt

[issue34007] test_gdb fails in s390x SLES buildbots

Pablo Galindo Salgado added the comment: I think I understand what is happening. The SLES buildbots do not have debugging symbols for glibc: (gdb) set verbose on (gdb) break builtin_id Reading in symbols for Python/bltinmodule.c...done. Breakpoint 1 at 0x139403c: file Python/bltinmodule.c, li

[issue34007] test_gdb fails in s390x SLES buildbots

Pablo Galindo Salgado added the comment: I requested a SLES VM in https://linuxone20.cloud.marist.edu as indicated by @David Edelsohn (the builtbot maintainer) and I can reproduce the issue on master, 3.7, 3.6 and 3.5. So it seems that a change in gdb itself caused this. Interestingly, in Py

[issue34007] test_gdb fails in s390x SLES buildbots

Pablo Galindo Salgado added the comment: This failure seems related to the issue: https://buildbot.python.org/all/#/builders/139/builds/74 = FAIL: test_threads (test.test_gdb.PyBtTests) Verify that "py-bt" indicates threads t

[issue34007] test_gdb fails in s390x SLES buildbots

Pablo Galindo Salgado added the comment: New failure on s390x SLES 3.7: https://buildbot.python.org/all/#/builders/122/builds/540 -- ___ Python tracker ___ _

[issue34007] test_gdb fails in s390x SLES buildbots

Karthikeyan Singaravelan added the comment: All the builds fail consistently after http://buildbot.python.org/all/#/builders/54/builds/465 and things were passing before 465. Maybe is this something to do with the commit that happened there that we could revert and test it in the machine by d

[issue34007] test_gdb fails in s390x SLES buildbots

STINNER Victor added the comment: In gdb source code, frame_unwind_pc(), I see: else if (this_frame->prev_pc.status == CC_NOT_SAVED) throw_error (OPTIMIZED_OUT_ERROR, _("PC not saved")); -- nosy: +vstinner ___ Python tracker

[issue34007] test_gdb fails in s390x SLES buildbots

New submission from Pablo Galindo Salgado : test_gdb is currently failing on the following buildbots: http://buildbot.python.org/all/#/builders/54/builds/465 http://buildbot.python.org/all/#/builders/66/builds/178 http://buildbot.python.org/all/#/builders/16/builds/1279 http://buildbot.python.o