[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#626482: marked as done (libc0.1: 2.13 causes segfaults + bus errors inside DSA's dchroots)

Your message dated Wed, 22 Oct 2014 00:17:50 +0100
with message-id <5446E99E.2020507@pyro.eu.org>
and subject line Re: Bug#626482: libc0.1: 2.13 causes segfaults + bus errors inside DSA's dchroots
has caused the Debian Bug report #626482,
regarding libc0.1: 2.13 causes segfaults + bus errors inside DSA's dchroots
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
626482: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=626482
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: libc0.1
Version: 2.13-2
Severity: important
User: debian-bsd@lists.debian.org
Usertags: kfreebsd

[Mostly a summary of
 http://lists.debian.org/debian-bsd/2011/05/msg00038.html and
 http://lists.debian.org/debian-bsd/2011/05/msg00039.html]

After dist-upgrading libc0.1 and friends (i.e. all(*) installed packages
which are also built from eglibc source) from 2.11.2-something to 2.13-2
inside io's and asdfasdf's sid, calling "dchroot sid" segfaults on io
and causes bus errors on asdfasdf:

io:~# dchroot sid /bin/true
Segmentation fault
io:~# dchroot sid
Segmentation fault
io:~# 

asdfasdf:~# dchroot sid /bin/true
Bus error
asdfasdf:~# dchroot sid
Bus error
asdfasdf:~# 

Ah normal (but root only) "chroot /srv/chroot/sid" works on both
machines, so I could at least fix it from the inside by downgrading
libc0.1 and friends back to 2.11.2-13.

Please note that the used dchroot command comes from DSA's version of
dchroot-dsa (version 2:1.1), not from the one in the Debian archive. The
latter does not show this problem according to Petr Salinger.

I'm not sure where exactly the causing bug is located, it could be in
eglibc, in DSA's dchroot, and maybe also in gcc-4.6 (with which libc0.1
2.13-2 very likely has been compiled). But as downgrading libc0.1 and
friends helped to fix this regression, I'm filing it against libc0.1.

I'm not filing this as RC as it is not yet reproducible with only
packages from the official archive, but since porterboxes are affected
I doubt that this is a less important issue.

So feel free to raise the severity and/or reassign this bug.

(*) locales is definitely not relevant here as I initially by accident
    just downgraded all architecture-dependent packages built from the
    eglibc source.

-- System Information:
Debian Release: wheezy/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: kfreebsd-i386 (i686)

Kernel: kFreeBSD 8.2-1-686
Locale: LANG=en_US.iso885915, LC_CTYPE=en_US.iso885915 (charmap=ISO-8859-15)
Shell: /bin/sh linked to /bin/dash

Versions of packages libc0.1 depends on:
ii  libc-bin                      2.13-2  Embedded GNU C Library: Binaries
ii  libgcc1                       1:4.6.0-7  GCC support library

Versions of packages libc0.1 recommends:
pn  libc0.1-i686                  <none>     (no description available)

Versions of packages libc0.1 suggests:
ii  debconf [debconf-2.0]         1.5.39     Debian configuration management sy
pn  glibc-doc                     <none>     (no description available)
ii  locales                       2.13-2  Embedded GNU C Library: National L
ii  locales-all [locales]         2.13-2  Embedded GNU C Library: Precompile

-- debconf information:
* glibc/restart-services: cron
  glibc/disable-screensaver:
  glibc/restart-failed:
  glibc/upgrade: true

--- End Message ---
--- Begin Message --- 
Source-Version: 2.19-11

Not reproducible with sid/jessie glibc.

Regards,
-- 
Steven Chamberlain
steven@pyro.eu.org

--- End Message ---
Reply to: