usb-creator-gtk crashed with SIGSEGV in malloc()

Bug #930958 reported by Mathieu Marquer
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
usb-creator (Ubuntu)
New
Undecided
Unassigned

Bug Description

Crashed when creating a live USB from Precise AMD64 daily-live, at the bootloader step.

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: usb-creator-gtk 0.2.34
ProcVersionSignature: Ubuntu 3.0.0-16.28-generic 3.0.17
Uname: Linux 3.0.0-16-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 1.23-0ubuntu4
Architecture: amd64
CrashCounter: 1
Date: Sun Feb 12 14:16:49 2012
ExecutablePath: /usr/bin/usb-creator-gtk
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Beta amd64 (20110901)
InterpreterPath: /usr/bin/python2.7
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/bin/usb-creator-gtk
ProcEnviron:
 PATH=(custom, no user)
 LANG=fr_FR.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7fbdae7b1d96: mov 0x8(%rbx),%rdx
 PC (0x7fbdae7b1d96) ok
 source "0x8(%rbx)" (0x100000007) not located in a known VMA region (needed readable region)!
 destination "%rdx" ok
 Stack memory exhausted (SP below stack segment)
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: usb-creator
StacktraceTop:
 ?? () from /lib/x86_64-linux-gnu/libc.so.6
 ?? () from /lib/x86_64-linux-gnu/libc.so.6
 malloc () from /lib/x86_64-linux-gnu/libc.so.6
 ?? ()
 PyEval_EvalFrameEx ()
Title: usb-creator-gtk crashed with SIGSEGV in malloc()
UpgradeStatus: Upgraded to oneiric on 2012-02-05 (6 days ago)
UserGroups:

Revision history for this message
Mathieu Marquer (slasher-fun) 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 #868462, 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.