synaptic crashed with SIGSEGV in pkgRecords::Lookup()

Bug #1117635 reported by green-elephant999
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
synaptic (Ubuntu)
New
Undecided
Unassigned

Bug Description

Crashed at the start, I didn't noticed it if weren't because of the warning. Maybe is not a problem after all.

ProblemType: Crash
DistroRelease: Ubuntu 13.04
Package: synaptic 0.80~exp1
ProcVersionSignature: Ubuntu 3.8.0-4.8-generic 3.8.0-rc6
Uname: Linux 3.8.0-4-generic x86_64
ApportVersion: 2.8-0ubuntu4
Architecture: amd64
Date: Thu Jan 31 21:48:05 2013
ExecutablePath: /usr/sbin/synaptic
InstallationDate: Installed on 2013-01-13 (23 days ago)
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
MarkForUpload: True
ProcCmdline: /usr/sbin/synaptic
ProcEnviron:
 LANGUAGE=en_GB:en
 PATH=(custom, no user)
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
 TERM=unknown
SegvAnalysis:
 Segfault happened at: 0x7f4aaa764634 <_ZN10pkgRecords6LookupERKN8pkgCache15VerFileIteratorE+20>: mov (%rax),%eax
 PC (0x7f4aaa764634) ok
 source "(%rax)" (0x7f50dd3d6000) not located in a known VMA region (needed readable region)!
 destination "%eax" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: synaptic
StacktraceTop:
 pkgRecords::Lookup(pkgCache::VerFileIterator const&) () from /usr/lib/x86_64-linux-gnu/libapt-pkg.so.4.12
 ?? ()
 ?? ()
 ?? ()
 ?? ()
Title: synaptic crashed with SIGSEGV in pkgRecords::Lookup()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

Revision history for this message
green-elephant999 (gergarfe) wrote :
Revision history for this message
Apport retracing service (apport) wrote : This bug is a duplicate

Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1097532, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.

information type: Private → Public
tags: removed: need-amd64-retrace
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.