whoopsie crashed with SIGSEGV in g_hash_table_foreach()

Bug #961147 reported by crescentstar
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
whoopsie-daisy (Ubuntu)
New
Undecided
Unassigned

Bug Description

while installing using ubuntu software center

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: whoopsie 0.1.18
ProcVersionSignature: Ubuntu 3.2.0-19.30-generic 3.2.11
Uname: Linux 3.2.0-19-generic x86_64
NonfreeKernelModules: fglrx
ApportVersion: 1.94.1-0ubuntu2
Architecture: amd64
CrashCounter: 1
Date: Wed Mar 21 15:03:00 2012
ExecutablePath: /usr/bin/whoopsie
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64 (20120316)
ProcCmdline: whoopsie
ProcEnviron:
 PATH=(custom, no user)
 TERM=linux
SegvAnalysis:
 Segfault happened at: 0x405122: repnz scas %es:(%rdi),%al
 PC (0x00405122) ok
 source "%es:(%rdi)" (0x00000000) not located in a known VMA region (needed readable region)!
 destination "%al" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: whoopsie-daisy
StacktraceTop:
 ?? ()
 g_hash_table_foreach () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 ?? ()
 ?? ()
 ?? ()
Title: whoopsie crashed with SIGSEGV in g_hash_table_foreach()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

Revision history for this message
crescentstar (ozgursuzailesi) 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 #960751, 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.

visibility: private → public
visibility: 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.