Hello all, So I've just gotten bit by a SEGFAULT during a dpkg upgrade using the 3.4 (or I guess gcc-4.0 archive). This occurred after --force'ing the /usr/lib64 issue with the libc6 upgrade. The messages can be found below. Any suggestions about how to fix this?
Thanks a bunch, Scott ---------------------------------------- Preparing to replace dpkg 1.10.25.0.0.1.gcc4 (using .../dpkg_1.10.27.0.0.1.gcc4_amd64.deb) ... Unpacking replacement dpkg ... E: Sub-process /usr/bin/dpkg received a segmentation fault. ... uller(root):/var/cache/apt/archives# dpkg --version Debian GNU/Linux `dpkg' package management program version 1.10.27 (amd64). This is free software; see the GNU General Public Licence version 2 or later for copying conditions. There is NO warranty. See dpkg --licence for copyright and license details. ... uller(root):/var/cache/apt/archives# gdb /usr/bin/dpkg GNU gdb 6.3-debian Copyright 2004 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "x86_64-linux"...(no debugging symbols found) Using host libthread_db library "/lib/libthread_db.so.1". (gdb) run -i dpkg_1.10.27.0.0.1.gcc4_amd64.deb Starting program: /usr/bin/dpkg -i dpkg_1.10.27.0.0.1.gcc4_amd64.deb (no debugging symbols found) (no debugging symbols found) Program received signal SIGSEGV, Segmentation fault. 0x0000002a956e39ba in strncasecmp () from /lib/libc.so.6 -- Scott M. Ransom Address: NRAO Phone: (434) 296-0320 520 Edgemont Rd. email: [EMAIL PROTECTED] Charlottesville, VA 22903 USA GPG Fingerprint: 06A9 9553 78BE 16DB 407B FFCA 9BFA B6FF FFD3 2989 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
