On Fri, Jun 10, 2005 at 11:36:18PM +0100, Jonathan David Amery wrote:
> I've just upgraded my system from woody to sarge. Among other upgrade=20
> problems I noticed that programmes like cp, mv and install were occasiona=
lly=20
> segfaulting (and the packages that were invoking them failing to get=20
> installed), leaving register dumps like this in my logs:
> Recompiling libacl1 (itself an awkward task since the package itself=20
> 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
Do you know if upgrading to the 2.4 kernel version available in sarge makes
a difference here?=20
--=20
Steve Langasek
postmodern programmer
--g6DVDhPhk1bqxDrC
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature
Content-Disposition: inline
Message-ID: <email address hidden>
Date: Fri, 10 Jun 2005 16:39:26 -0700
From: Steve Langasek <email address hidden>
To: Jonathan David Amery <email address hidden>,
<email address hidden>
Cc: <email address hidden>
Subject: Re: Bug#312936: Programmes linked against libacl1 segfault in libacl1 code.
--g6DVDhPhk1bqxDrC Disposition: inline Transfer- Encoding: quoted-printable
Content-Type: text/plain; charset=us-ascii
Content-
Content-
On Fri, Jun 10, 2005 at 11:36:18PM +0100, Jonathan David Amery wrote:
> I've just upgraded my system from woody to sarge. Among other upgrade=20
> problems I noticed that programmes like cp, mv and install were occasiona=
lly=20
> segfaulting (and the packages that were invoking them failing to get=20
> 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=
=20
> libacl1:
> libacl.so.1 =3D> /lib/libacl.so.1 (0x40026000)
> libc.so.6 =3D> /lib/libc.so.6 (0x40034000)
> libattr.so.1 =3D> /lib/libattr.so.1 (0x40159000)
> /lib/ld-linux.so.2 =3D> /lib/ld-linux.so.2 (0x40000000)
> libgcc_s.so.1 =3D> /lib/libgcc_s.so.1 (0x40164000)
> Recompiling libacl1 (itself an awkward task since the package itself=20
> 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
Do you know if upgrading to the 2.4 kernel version available in sarge makes
a difference here?=20
--=20
Steve Langasek
postmodern programmer
--g6DVDhPhk1bqxDrC pgp-signature; name="signature .asc" Description: Digital signature Disposition: inline
Content-Type: application/
Content-
Content-
-----BEGIN PGP SIGNATURE-----
ufymYLloRAsfBAK CZC7h+stBLENk5g EnXR7AAl3Gm1wCg uDb6 hkIoSh80=
Version: GnuPG v1.4.1 (GNU/Linux)
iD8DBQFCqiStKN6
HhucLyUlb48LET+
=/8I5
-----END PGP SIGNATURE-----
--g6DVDhPhk1bqx DrC--