Bug 2063942

Summary: Backport "GC_init SEGV while in gdb" fix
Product: [Fedora] Fedora Reporter: Alexandra Petlanová Hájková <ahajkova>
Component: gcAssignee: Alexandra Petlanová Hájková <ahajkova>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: urgent    
Version: rawhideCC: 8ru2u4gz, aburgess, fche, kevinb, noobusinghacks, paulo.cesar.pereira.de.andrade, praiskup, rdieter
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: gc-8.0.6-3.fc37 gc-8.0.6-3.fc36 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2022-06-29 02:07:23 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Alexandra Petlanová Hájková 2022-03-14 16:51:10 UTC
Description of problem:
When running gdb under gdb on Rawhide gdb segfaults during gc initialization,
this was recently fixed upstream. Please backport "Do not probe to find main data root start if dl_iterate_phdr exists" fix, https://github.com/ivmai/bdwgc/issues/432


Version-Release number of selected component (if applicable):
gc-8.0.6-2.fc36.x86_64

Comment 1 Alexandra Petlanová Hájková 2022-05-17 17:34:04 UTC
This is now affecting all GDB / GC users on Fedora 36 and Fedora Rawhide.

Comment 2 Alexandra Petlanová Hájková 2022-06-17 08:17:47 UTC
Backport merged:
https://src.fedoraproject.org/rpms/gc/pull-request/6

Comment 3 Kevin Buettner 2022-06-22 01:31:26 UTC
I think a similar pull request will need to be created for F36.

Comment 4 Kevin Buettner 2022-06-22 01:35:19 UTC
*** Bug 2096473 has been marked as a duplicate of this bug. ***

Comment 5 Kevin Buettner 2022-06-23 20:56:21 UTC
*** Bug 2100443 has been marked as a duplicate of this bug. ***

Comment 6 Fedora Update System 2022-06-27 23:26:21 UTC
FEDORA-2022-4a37df6a10 has been submitted as an update to Fedora 36. https://bodhi.fedoraproject.org/updates/FEDORA-2022-4a37df6a10

Comment 7 Fedora Update System 2022-06-28 01:10:17 UTC
FEDORA-2022-4a37df6a10 has been pushed to the Fedora 36 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2022-4a37df6a10`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-4a37df6a10

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 8 Fedora Update System 2022-06-29 02:07:23 UTC
FEDORA-2022-4a37df6a10 has been pushed to the Fedora 36 stable repository.
If problem still persists, please make note of it in this bug report.