This bug was fixed in the package apt - 0.8.16~exp12ubuntu10.25
---
apt (0.8.16~exp12ubuntu10.25) precise; urgency=medium
* Backport patches from David Kalnischkies to fix crashes with dynamic
cache remapping (LP: #957231):
- Do not dereference the storage for the unique
Hm, I didn't enable proposed for that ppa. There was no need, because
only i386 builds were affected and we use amd64. I can confirm new i386
builds worked, but with no action on my part.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Only i386 builds were affected, but that included all Architecture: all
builds. Peculiar. My best speculation is that perhaps a change in
precise-updates was enough to perturb away the apt bug, but then that
allowed the PPA to also change so that now even a combination of
precise-updates at the
Unfortunately, despite my best efforts, my reproduction case went away -
I think due to changes in the PPA in question. They may actually have
enabled -proposed to get them out of the hole they were stuck in, but I
can't tell directly. I've done some basic regression testing on the new
version
Hello cliff, or anyone else affected,
Accepted apt into precise-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/apt/0.8.16~exp12ubuntu10.25 in a
few hours, and then in the -proposed repository.
Please help us by testing this new package. See
** Branch linked: lp:ubuntu/precise-proposed/apt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/957231
Title:
update-manager crashed with SIGSEGV in
debListParser::LoadReleaseInfo()
To manage
** Changed in: apt (Ubuntu Precise)
Status: Triaged = In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/957231
Title:
update-manager crashed with SIGSEGV in
This also caused some Landscape private PPA builds to segfault
mysteriously. After tracking it down to this bug, I've uploaded an SRU,
currently awaiting review. That should also provide a useful test case.
** Changed in: apt (Ubuntu Precise)
Assignee: (unassigned) = Colin Watson
** Changed in: apt (Ubuntu Saucy)
Status: Triaged = Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/957231
Title:
update-manager crashed with SIGSEGV in
Any update on the SRU for Precise?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/957231
Title:
update-manager crashed with SIGSEGV in
debListParser::LoadReleaseInfo()
To manage notifications
This sounds like its worthwhile to SRU the attached apt diff from commit
2b803d4069e1f05d0461fbad004482ff02100812
** Also affects: apt (Ubuntu Saucy)
Importance: Undecided
Status: New
** Also affects: apt (Ubuntu Precise)
Importance: Undecided
Status: New
** Changed in: apt
This issue is much more prevalent on Saucy than on Precise.
92k crashes reported on Saucy vs
3k crashes reported on Precise
https://errors.ubuntu.com/bucket/?id=/usr/bin/update-
** Changed in: apt (Ubuntu Saucy)
Importance: Undecided = High
** Changed in: apt (Ubuntu Saucy)
Status: New = Triaged
** Changed in: apt (Ubuntu Precise)
Status: New = Triaged
** Changed in: apt (Ubuntu Precise)
Importance: Undecided = Medium
--
You received this bug
** No longer affects: update-manager (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/957231
Title:
update-manager crashed with SIGSEGV in
debListParser::LoadReleaseInfo()
To manage
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: update-manager (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/957231
** Also affects: update-manager (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/957231
Title:
update-manager crashed with SIGSEGV in
My sources, as requested.
** Attachment added: apt sources
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/957231/+attachment/3903834/+files/apt%20Sources.tar.gz
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Also affects: apt (Ubuntu Trusty)
Importance: Medium
Status: Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/957231
Title:
update-manager crashed with SIGSEGV in
This seems to be a recurrence of bug 854090 which doesn't seem to have
actually been fixed.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/957231
Title:
update-manager crashed with SIGSEGV in
** Tags added: bugpattern-needed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/957231
Title:
update-manager crashed with SIGSEGV in
debListParser::LoadReleaseInfo()
To manage notifications about
** Tags added: saucy
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/957231
Title:
update-manager crashed with SIGSEGV in
debListParser::LoadReleaseInfo()
To manage notifications about this bug go
Looking at the Ubuntu Error Tracker we can see that this is still
occurring (https://errors.ubuntu.com/bucket/?id=/usr/bin/update-
manager:11:debListParser::LoadReleaseInfo:debPackagesIndex::Merge:BuildCache:pkgCacheGenerator::MakeStatusCache:pkgCacheFile::BuildCaches)
with apt version
The failing line of code is:
case Origin: FileI-Origin = WriteUniqString(data); break;
I suspect this might be a problem with the complex C++ gadgets that
handle writing into apt's cache, but it's hard to tell. I further
suspect that this is quite strongly dependent on things like the exact
Colin is right, its about remapping. WriteUniqString() can cause the
underlying data storage to move. FileI is registered to be rewritten to
accommodate the move, but the compiler already has the address
calculated so the rewrite of FileI is too late.
The line must be split into
map_ptrloc foobar
Colin, I hope this helps..See Attachements
On Wed, Apr 3, 2013 at 10:36 AM, Colin Watson cjwat...@canonical.comwrote:
The failing line of code is:
case Origin: FileI-Origin = WriteUniqString(data); break;
I suspect this might be a problem with the complex C++ gadgets that
handle writing
** Information type changed from Private to Public
** Package changed: update-manager (Ubuntu) = apt (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/957231
Title:
update-manager crashed
26 matches
Mail list logo
