This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author pablogsal
Recipients pablogsal, vstinner, xtreak
Date 2018-08-27.21:48:40
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1535406520.52.0.56676864532.issue34007@psf.upfronthosting.co.za>
In-reply-to
Content
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, line 1182.
(gdb) r
Starting program: /home/linux1/cpython/python tester.py
Reading symbols from /lib/ld64.so.1...(no debugging symbols found)...done.
Reading symbols from system-supplied DSO at 0x3fffdffe000...(no debugging symbols found)...done.
Missing separate debuginfos, use: zypper install glibc-debuginfo-2.22-62.13.2.s390x
Reading symbols from /lib64/libpthread.so.0...(no debugging symbols found)...done.
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib64/libthread_db.so.1".
Reading symbols from /lib64/libdl.so.2...(no debugging symbols found)...done.
Reading symbols from /lib64/libutil.so.1...(no debugging symbols found)...done.
Reading symbols from /lib64/libm.so.6...(no debugging symbols found)...done.
Reading symbols from /lib64/libc.so.6...(no debugging symbols found)...done.

And when requesting the stacktrace of a thread it cannot go into libc because the program counter is not available:

(gdb) thread apply 2 where

#19 0x0000000001324f02 in method_call (method=<method at remote 0x3fffdeee258>, args=(), kwargs=0x0) at Objects/classobject.c:306
#20 0x0000000001047396 in PyObject_Call (callable=<method at remote 0x3fffdeee258>, args=(), kwargs=0x0) at Objects/call.c:245
#21 0x00000000012b91be in t_bootstrap (boot_raw=0x3fffd9fb118) at ./Modules/_threadmodule.c:992
#22 0x000003fffde88b22 in start_thread () from /lib64/libpthread.so.0
#23 0x000003fffdb7164a in thread_start () from /lib64/libc.so.6
PC not saved

This get triggered when printing the python stack trace with py-bt and the exception is getting printed on stderr and this fails the test.
History
Date User Action Args
2018-08-27 21:48:40pablogsalsetrecipients: + pablogsal, vstinner, xtreak
2018-08-27 21:48:40pablogsalsetmessageid: <1535406520.52.0.56676864532.issue34007@psf.upfronthosting.co.za>
2018-08-27 21:48:40pablogsallinkissue34007 messages
2018-08-27 21:48:40pablogsalcreate