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-29.21:22:58
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
Interestingly, everything points to something special in the glibc version of the buildbot. Usually the end of the stack for threads is:

#22 0x00007ffff7f82a9d in start_thread () from /usr/lib/
#23 0x00007ffff7d23a43 in clone () from /usr/lib/

but in this buildbot we get:

#24 0x000003fffde88b22 in start_thread () from /lib64/
#25 0x000003fffdb7164a in thread_start () from /lib64/
PC not saved

I think that the combination of glibc + gdb is producing this problem probably because the optimization level of glibc.
Date User Action Args
2018-08-29 21:22:58pablogsalsetrecipients: + pablogsal, vstinner, xtreak
2018-08-29 21:22:58pablogsalsetmessageid: <>
2018-08-29 21:22:58pablogsallinkissue34007 messages
2018-08-29 21:22:58pablogsalcreate