Bug#403985: apt-get update crashes in pkgAcqDiffIndex::ParseDiffIndex
Yay, I got this fixed.
As a temporary workaround, I found that by removing the files in /var/lib/apt/lists, I was able to avoid having that ParseDiffIndex function called.
Then I rembered that when I installed the system, unstable had a bug in libattr (I think) that caused ls and many other very basic utilities to stop working. Some of the other packages on my system were
apparently messed up from that, so I just did a reinstall of every package on the system. Now apt-get update runs without a crash. No idea what was *actually* causing the crash, but I guess it's not such
a pressing matter anymore.
I'm pretty new to the Debian bug tracking system. Should this bug be changed now?
Thanks,
Jacob
On 1/2/07, jacob kuenzel <
jayekub@gmail.com> wrote:I took another look and have a little more info to add. The crash seems to be occuring sometime shortly after line 253 of apt-pkg/acquire-
item.cc (in the apt-0.6.46.4 source tree), but still within pkgAcqDiffIndex::ParseDiffIndex. Here's some useful debugging output and the contents of the file that appears to be causing the crash:
$ apt-get -o Debug::pkgAcquire::Diffs=yes update
...
pkgAcqDiffIndex::Done():
http://cudlug.cudenver.edu/debian/dists/unstable/main/binary-i386/Packages.diff/Index
Renaming: /var/lib/apt/lists/partial/cudlug.cudenver.edu_debian_dists_unstable_main_binary-i386_Packages.DiffIndex -> /var/lib/apt/lists/cudlug.cudenver.edu_debian_dists_unstable_main_binary-i386_Packages.IndexDiff
pkgAcqIndexDiffs::ParseIndexDiff() /var/lib/apt/lists/cudlug.cudenver.edu_debian_dists_unstable_main_binary-i386_Packages.IndexDiff
SHA1-Current: b12c5c4968ede9e0428c49796f4e13abb8e026f2
Segmentation fault
$ cat /var/lib/apt/lists/cudlug.cudenver.edu_debian_dists_unstable_main_binary-i386_Packages.IndexDiff
SHA1-Current: b12c5c4968ede9e0428c49796f4e13abb8e026f2 20613927
SHA1-History:
93f5953d2a03902023ba5624bc8da4b3d2d473ae 20526418
2006-12-25-2016.38
f00607beb9f3f36206e69c1782c23dd003e47f37 20526444 2006-12-26-0805.32
81adfc964da383566d2263cf92086de7cda6ad75 20536050 2006-12-26-2005.41
5bcf6fff0b2a44216693782a188b67e506c8f616 20535986 2006-12-27-0804.21
7e1e1d38cbe8c49418e13ae90a22be856936c1c0 20536276 2006-12-27-2005.08
ce59ab38e35cd170e0ac2253373cdcd2b9b482c1 20536351 2006-12-28-0807.03
93dea4bd967c35435f7305cebbab82b498b46bf4 20536614 2006-12-28-2007.05
f766595b8035acaff14267b58bd930f0962f7d68 20612929 2006-12-29-0805.37
c101ea4da46070ccbdaac779c4e7312a7e1b9f66 20612955 2006-12-29-2008.23
7b24a5986028661bb4dd4418dd49225123f6e755 20613860 2006-12-30-0804.54
3b44ebefa41593b68889b4104510fc64118b3862 20614357
2006-12-30-2005.41
de7f7a45b239c15a1cfe3d64a5a207999ce994c6 20614582 2006-12-31-0813.17
6201fbd67518b8bc029b7f89f0eb60a3622ca4a8 20614570 2006-12-31-2008.12
8bd1996caa183e0f69ccd0ada7a9686befd0ab72 20613902 2007-01-01-0804.47
SHA1-Patches:
13dbb5c6f4d4d34a53d4d253bb050637bc59a451 5816 2006-12-25-2016.38
a829c47a33035f1b3bd272cc3642e176515d975d 13605 2006-12-26-0805.32
ca6359949e6aae79e6a9054ce17aa361205e9195 17250 2006-12-26-2005.41
5b1d8fc212c468a8da2b9ead08d497edc894f715 16075 2006-12-27-0804.21
f9d0344674244016b5b858408d751196135ee911 3751 2006-12-27-2005.08
6455e8256617a7c056f5751d9ed6fdd0d44a5a27 16242 2006-12-28-0807.03
76dc867ec0e6eb49435397f19946386f5ff3a472 108675
2006-12-28-2007.05
4126ecddf2a151fbb61486683ec964cad4897424 26446 2006-12-29-0805.37
80a09e41c189c06d472710b124b595c5e2c5e286 48535 2006-12-29-2008.23
65bab1a70c4afcdeb4c65e6c8b8760dd654437ca 31693 2006-12-30-0804.54
0c43c2c83ecd2149e13410931937f17253514ea4 14777 2006-12-30-2005.41
5df43b0fbc7f125adb46b358eafd19bb7cfafa0d 13888 2006-12-31-0813.17
e4cdb010b1766ae7e400f924d224a73918116993 20203 2006-12-31-2008.12
f5e5278c2753052d7a1d87649d53556d423d0edf 2762
2007-01-01-0804.47
I'll add more if I get the time/motivation.
Jacob
On 1/2/07,
jacob kuenzel <
jayekub@gmail.com> wrote:Hey,
No problem, I was on vacation and just got back.
Yes, since I haven't been able to update any packages on my system the error is still happening. Moving those .bin files out of the way seemed to have no effect. I have the latest version of apt in unstable
and reinstalling the .deb didn't seem to help either...
Unless anyone out there has any bright ideas about this I'm just going to re-install the system and hope it goes away. If not, then it's pretty clearly a serious problem and I'll report back.
Thanks,
Jacob
On 12/28/06, Andreas Barth <
aba@not.so.argh.org> wrote:
Hi,
sorry that nobody contacted you for such a long time.
* jacob kuenzel (jayekub@gmail.com) [061220 18:50]:
> I just did a fresh install from the stable netinst iso and then
> dist-upgraded to unstable. Now when I try to aptitude update or
> apt-get update, I get a crash:
does this error still happen for you? I couldn't reproduce it. If so,
could you try moving away /var/cache/apt/*bin and if it works after
that?
Cheers,
Andi
--
http://home.arcor.de/andreas-barth/
Reply to: