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

Re: Segfault on apt-get (sarge)



Geert Uytterhoeven wrote:
Usually libc6 is too blame. If you still have the old one in
/var/cache/apt/archives/ (or can get it on the box) just reinstall it manually.

Tried rolling back to libc6_2.3.2-9, but that didn't help. I'm not exactly sure what I was running before, and of course I did an `apt-get clean` out of habit.

So I'm seeing this both with that libc and with libc6_2.3.2.ds1-10. And changing the cache limit didn't fix it, either.

# gdb apt-get
GNU gdb 6.0-debian

[snipped]

(gdb) run update

[snipped]

Reading Package Lists... 0%
Program received signal SIGSEGV, Segmentation fault.
0x0ffb0094 in pkgCacheGenerator::ListParser::NewDepends(pkgCache::VerIterator, std::string, std::string, unsigned, unsigned) () from /usr/lib/libapt-pkg-libc6.3-5.so.3.3
(gdb) bt
#0 0x0ffb0094 in pkgCacheGenerator::ListParser::NewDepends(pkgCache::VerIterator, std::string, std::string, unsigned, unsigned) () from /usr/lib/libapt-pkg-libc6.3-5.so.3.3 #1 0x0ffb0054 in pkgCacheGenerator::ListParser::NewDepends(pkgCache::VerIterator, std::string, std::string, unsigned, unsigned) () from /usr/lib/libapt-pkg-libc6.3-5.so.3.3
#2  0x0ffbc32c in debListParser::NewVersion(pkgCache::VerIterator) ()
   from /usr/lib/libapt-pkg-libc6.3-5.so.3.3
#3 0x0ffaed78 in pkgCacheGenerator::MergeList(pkgCacheGenerator::ListParser&, pkgCache::VerIterator*) () from /usr/lib/libapt-pkg-libc6.3-5.so.3.3 #4 0x0ffc9a4c in debPackagesIndex::Merge(pkgCacheGenerator&, OpProgress&) const ()
   from /usr/lib/libapt-pkg-libc6.3-5.so.3.3
#5 0x0ffb188c in pkgCacheGenerator::WriteUniqString(char const*, unsigned) ()
   from /usr/lib/libapt-pkg-libc6.3-5.so.3.3
#6 0x0ffb1cf8 in pkgMakeStatusCache(pkgSourceList&, OpProgress&, MMap**, bool) ()
   from /usr/lib/libapt-pkg-libc6.3-5.so.3.3
#7  0x0ffa7cec in pkgCacheFile::BuildCaches(OpProgress&, bool) ()
   from /usr/lib/libapt-pkg-libc6.3-5.so.3.3
#8  0x1000d2fc in ?? ()
(gdb)

--
Ken Treis
Miriam Technologies, Inc.



Reply to: