Bug 1244916 - glibc segfaults immediately after chrooting into the stage2 bootstrap environment
Summary: glibc segfaults immediately after chrooting into the stage2 bootstrap environ...
Alias: None
Product: Fedora
Classification: Fedora
Component: glibc
Version: 21
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
Assignee: Carlos O'Donell
QA Contact: Fedora Extras Quality Assurance
Depends On:
Blocks: fedora-bootstrap
TreeView+ depends on / blocked
Reported: 2015-07-20 18:37 UTC by Jaromír Cápík
Modified: 2016-11-24 12:03 UTC (History)
11 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2015-09-16 13:43:41 UTC

Attachments (Terms of Use)

Description Jaromír Cápík 2015-07-20 18:37:02 UTC
Description of problem:
During the stage2 bootstrap we experience glibc segfaults when chrooting into the minimal environment. The issue only happens for some combinations of builder and target architectures.

Since it's difficult to collect sufficient debug data, we offer an access to the build environment where we're able to reproduce the issue.

I tried to do a diff of the nm output for a working and non-working libc.so.* and both contain the same symbols. However they differ in addresses and that probably means the generated code differs.

Version-Release number of selected component (if applicable):

How reproducible:

Comment 1 Carlos O'Donell 2015-07-20 19:14:17 UTC
Arch? I think you saw this on aarch64?

Comment 2 Jaromír Cápík 2015-07-24 09:39:12 UTC
It applies to multiple architectures. aarch64 is just one of them. Right know I'm sure it's reproducible with all B=T rootfs except x86_64.

Comment 3 Jeff Law 2015-07-24 21:43:11 UTC
Adding DJ as we expect he'll be lending a hand on getting the bootstrapping process going.

Comment 4 DJ Delorie 2015-09-11 01:34:28 UTC
Turns out the root cause of this problem is this line in stage1's glibc recipe:

echo libc_cv_ctors_header=yes >> config.cache

Commenting out or removing that line should fix it.

Comment 5 Jaromír Cápík 2015-09-14 16:18:25 UTC
Thanks guys. Gonna try.

Comment 6 Jaromír Cápík 2015-09-16 13:43:41 UTC
Seems to work for all previously failing combinations. I couldn't test s390 due to an outage, but I believe it's ok too.

Thanks a lot for the fix.

Note You need to log in before you can comment on or make changes to this bug.