Re: Bug#740068: debian-installer: segfaults when built against testing
Hi,
On Tue, Feb 25, 2014 at 02:39:23PM +0300, Cyril Brulebois wrote:
> Cyril Brulebois <kibi@debian.org> (2014-02-25):
> > Cyril Brulebois <kibi@debian.org> (2014-02-25):
> > > It doesn't seem to happen when building against unstable, but it
> > > would be nice to make sure we spot the reason/bugfix and possibly
> > > speed up its propagation to testing.
> >
> > I forgot to mention it's netboot/gtk/mini.iso on amd64, in case it
> > matters.
>
> So here are the results of some cross tests, using this:
> git clean -xdf && make rebuild_netboot-gtk USE_UDEBS_FROM=...
>
>
> chroot \ USE_UDEBS_FROM | jessie | sid
> ---------------------------------------------
> jessie | OK | segfault
> ---------------------------------------------
> sid | segfault | OK
>
> (FTR my chroots are up-to-date and sid's has 2.18-3.)
>
> This might be due to some libc mismatch (2.17 vs. 2.18) I guess?
Yes, we get this bug happening regularly because the binaries on the
image went through the library reduction process with a given libc (here
2.18), and later a different version of the libc is unpacked over it
(here 2.17). Therefore some symbols are missings, causing the segfault.
In addition I think there are also some version mismatches between libnss-*
and libc6 when the old one is getting unpacked.
> This rings some bells:
> | eglibc (2.18-2) unstable; urgency=medium
> |
> | [ Aurelien Jarno ]
> | * any/local-ldconfig-ignore-ld.so.diff: new patch to ignore the dynamic
> | linker in ldconfig. Closes: #699206, #707185, #727786, #736097,
> | #739734, #739758.
No it's not related to that. This bug is when you have multiple libc of
the same architecture on a system (e.g. libc6:amd64 and
libc6-amd64:i386, or libc6:i386 and libc-i386:amd64)
> eglibc maintainers, can you please suggest further directions for me to
> look into? Initial d-i bug report with busybox sh segfaults:
> http://bugs.debian.org/740068
>
You just have to ensure that the libc used for building the image is the
same as the one used later in d-i.
--
Aurelien Jarno GPG: 1024D/F1BCDB73
aurelien@aurel32.net http://www.aurel32.net
Reply to: