I had a similar segfault issue in version 1.0.9.5, though in a
different place:
#0 0xb7f604e7 in debStatusIndex::Merge(pkgCacheGenerator,
OpProgress*) const () from /usr/lib/i386-linux-gnu/libapt-pkg.so.4.12
#1 0xb7ebddb4 in ?? () from /usr/lib/i386-linux-gnu/libapt-pkg.so.4.12
#2
And after a few update/upgrade cycles using the
APT::Cache-Start=1, it is now working correctly again... I
guess because of the 0.9.7.5 upgrade of libapt-pkg4.12
Thanks,
Marc
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble?
Package: libapt-pkg4.12
Version: 0.9.7.4
Followup-For: Bug #674951
I'm having segfault when using aptitude/apt-get/dselect:
$ sudo apt-get update
...
[ 1741.499021] apt-get[4759]: segfault at 7fad99d27144 ip 7fad9b35f5f0 sp
7fffbc44f2e0 error 6 in
On Sat, Jun 16, 2012 at 6:48 AM, Grigory Ivanov
grundik-...@grundik.spb.ru wrote:
Another crash in version 0.9.6 with similar conditions:
[…]
Are these crashes reproducible?
If so, does it still crash if you do:
rm -f /var/cache/apt/*.bin
?
Or if you do
rm -f /var/cache/apt/*.bin
apt-get
On 16.06.2012 10:40, David Kalnischkies wrote:
Another crash in version 0.9.6 with similar conditions:
[Â…]
Are these crashes reproducible?
They were 100% reproducible at the time of bug filing. They are not
reproducible now, probably because changed(updated) package lists. But
aptitude
Another crash in version 0.9.6 with similar conditions:
Core was generated by `aptitude update'.
Program terminated with signal 11, Segmentation fault.
#0 0x7f2190cbe322 in
debListParser::NewVersion(pkgCache::VerIterator) () from
/usr/lib/x86_64-linux-gnu/libapt-pkg.so.4.12
(gdb) backtrace
Package: libapt-pkg4.12
Version: 0.9.5.1
Severity: normal
--- Please enter the report below this line. ---
aptitude update causes segmentation fault in libapt-pkg.so.4.12:
Program terminated with signal 11, Segmentation fault.
#0 0xb72c8461 in
7 matches
Mail list logo
