Bug 2211429

Summary: python3.7's test_gdb fails on rawhide with the latest gdb on i686
Product: [Fedora] Fedora Reporter: Charalampos Stratakis <cstratak>
Component: gdbAssignee: Kevin Buettner <kevinb>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: unspecified    
Version: rawhideCC: ahajkova, blarsen, fweimer, jan, keiths, kevinb, mcermak, mkolar
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2023-06-14 01:11:54 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
full build log none

Description Charalampos Stratakis 2023-05-31 15:33:33 UTC 
Trying to build python3.7 on rawhide currently fails on i686 with the latest gdb. Last successful build was with gdb-12.1-10.fc38. Not sure on which version the issue appeared as koschei doesn't built for i686. It might not even be a gdb issue but filling the bug against it for more info.

The error message:

A fatal error internal to GDB has been detected, further
debugging is not possible.  GDB will now terminate.
This is a bug, please report it.  For instructions, see:
<https://www.gnu.org/software/gdb/bugs/>.
Function "builtin_id" not defined.
warning: Unable to open "librpm.so.9" (librpm.so.9: cannot open shared object file: No such file or directory), missing debuginfos notifications will not be displayed
Missing separate debuginfo for /lib/libc.so.6.
The debuginfo package for this file is probably broken.
Missing separate debuginfo for /lib/libm.so.6.
The debuginfo package for this file is probably broken.
Fatal glibc error: malloc.c:2589 (sysmalloc): assertion failed: (old_top == initial_top (av) && old_size == 0) || ((unsigned long) (old_size) >= MINSIZE && prev_inuse (old_top) && ((unsigned long) old_end & (pagesize - 1)) == 0)
Fatal signal: Aborted

Reproducible: Always
Comment 1 Charalampos Stratakis 2023-05-31 15:34:30 UTC 
Created attachment 1968120 [details]
full build log
Comment 2 Kevin Buettner 2023-06-03 20:21:50 UTC 
FWIW, there was a recent soname bump for librpm - that's probably the reason for the librpm warnings.

Any thoughts about how I might reproduce this crash outside of the build environment?

I'm also curious about why python3.7 is being built...
Comment 3 Charalampos Stratakis 2023-06-06 00:42:15 UTC 
(In reply to Kevin Buettner from comment #2)
> FWIW, there was a recent soname bump for librpm - that's probably the reason
> for the librpm warnings.
> 
> Any thoughts about how I might reproduce this crash outside of the build
> environment?
> 
> I'm also curious about why python3.7 is being built...

Python 3.7 is being rebuilt to fix the high severity CVE-2023-24329

test_gdb works only on source builds so in order to reproduce it you'll have to clone the repository and test it out in a mock environment.

Within mock:
$ dnf builddep python3
$ git clone https://github.com/python/cpython.git
$ ./configure && make && ./python -m test -vv test_gdb

Interestingly enough I managed to reproduce it also on the main branch of CPython on 64 bits mock and also I've managed to fix it by doing a $ dnf debuginfo-install glibc libxcrypt.

However. I noticed that test_gdb is skipped on PGO builds from Python3.8 and onward: https://bugs.python.org/issue37023

On Python3.6 we skip test_gdb entirely. So I believe the proper course of action would be to skip test_gdb for python3.7's build.
Comment 4 Fedora Update System 2023-06-07 13:15:59 UTC 
FEDORA-2023-dd526ed2e4 has been submitted as an update to Fedora 37. https://bodhi.fedoraproject.org/updates/FEDORA-2023-dd526ed2e4
Comment 5 Fedora Update System 2023-06-07 13:19:00 UTC 
FEDORA-2023-f52390b9d2 has been submitted as an update to Fedora 38. https://bodhi.fedoraproject.org/updates/FEDORA-2023-f52390b9d2
Comment 6 Fedora Update System 2023-06-08 01:44:32 UTC 
FEDORA-2023-f52390b9d2 has been pushed to the Fedora 38 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2023-f52390b9d2`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2023-f52390b9d2

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
Comment 7 Fedora Update System 2023-06-08 02:22:11 UTC 
FEDORA-2023-dd526ed2e4 has been pushed to the Fedora 37 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2023-dd526ed2e4`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2023-dd526ed2e4

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
Comment 8 Fedora Update System 2023-06-14 01:11:54 UTC 
FEDORA-2023-f52390b9d2 has been pushed to the Fedora 38 stable repository.
If problem still persists, please make note of it in this bug report.
Comment 9 Fedora Update System 2023-06-16 02:14:57 UTC 
FEDORA-2023-dd526ed2e4 has been pushed to the Fedora 37 stable repository.
If problem still persists, please make note of it in this bug report.