Your message dated Sat, 28 May 2011 09:28:35 +0200
with message-id <[email protected]>
and subject line Re: [arm] Programmes linked against libacl1 segfault in 
libacl1 code
has caused the Debian Bug report #312936,
regarding [arm] Programmes linked against libacl1 segfault in libacl1 code
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 [email protected]
immediately.)


-- 
312936: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=312936
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: libacl1
Version: 2.2.23-1
Severity: critical
Justification: breaks unrelated software

I've just upgraded my system from woody to sarge.  Among other upgrade 
problems I noticed that programmes like cp, mv and install were occasionally 
segfaulting (and the packages that were invoking them failing to get 
installed), leaving register dumps like this in my logs:

  pc : [<400278ac>]    lr : [<4002a348>]    Not tainted
  sp : bffff4f4  ip : 40049cf8  fp : bffff780
  r10: 400333bc  r9 : bffffa38  r8 : bffff548
  r7 : bffff561  r6 : 00000000  r5 : 0001c324  r4 : bffff50c
  r3 : 00000004  r2 : 00000000  r1 : 00009d6b  r0 : bffff508
  Flags: nzCv  IRQs on  FIQs on  Mode USER_32  Segment user
  Control: 1C14917D  Table: 1C14917D  DAC: 00000015

Looking at the ldd output for cp makes it quite clear that this is inside 
libacl1:

        libacl.so.1 => /lib/libacl.so.1 (0x40026000)
        libc.so.6 => /lib/libc.so.6 (0x40034000)
        libattr.so.1 => /lib/libattr.so.1 (0x40159000)
        /lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x40000000)
        libgcc_s.so.1 => /lib/libgcc_s.so.1 (0x40164000)

Recompiling libacl1 (itself an awkward task since the package itself 
segfaults in the middle when it is doing something to the postinst script)
and installing the recompiled version fixes the problem.


-- System Information:
Debian Release: 3.1
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: arm (armv4l)
Kernel: Linux 2.4.18-rmk7
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)

Versions of packages libacl1 depends on:
ii  libattr1                    2.4.16-1     Extended attribute shared library
ii  libc6                       2.3.2.ds1-22 GNU C Library: Shared libraries an
ii  libgcc1                     1:3.4.3-13   GCC support library

-- no debconf information


--- End Message ---
--- Begin Message ---
Hi

> I've just upgraded my system from woody to sarge.  Among other upgrade
> problems I noticed that programmes like cp, mv and install were
occasionally
> segfaulting (and the packages that were invoking them failing to get

woody and sarge are long gone. The bug was specific to old kernel or
toolchain, so I'm closing this bug.

Cheers

Luk


--- End Message ---

Reply via email to