Hi Scott,
El miÃ, 16-03-2005 a las 13:32 -0500, Scott Ransom escribiÃ: > 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? What version of libc6 are you using? I cannot reproduce this using the gcc-4.0 archive and my version of dpkg seems to be the same than yours. Also note that given that you already took the time to run the program inside gdb, it usually helps a bit to have a backtrace (command bt) to know a bit more about where the program is when it fails. However, when programs don't have debug symbols and are optimized, as it's probably the case here, it won't tell much. Greetings, -- Javier Kohen <[EMAIL PROTECTED]> ICQ: blashyrkh #2361802 Jabber: [EMAIL PROTECTED]
signature.asc
Description: Esta parte del mensaje =?ISO-8859-1?Q?est=E1?= firmada digitalmente
