gpart crashed with SIGFPE in __libc_start_main()

Bug #272957 reported by StoatWblr
12
This bug affects 1 person
Affects Status Importance Assigned to Milestone
gpart (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

Binary package hint: gpart

crashed at startup while attempting to scan a 250Gb drive with trashed partition table

ProblemType: Crash
Architecture: i386
Dependencies:
 libgcc1 1:4.3.2-1ubuntu7
 gcc-4.3-base 4.3.2-1ubuntu7
 findutils 4.4.0-2ubuntu3
 libc6 2.8~20080505-0ubuntu6
DistroRelease: Ubuntu 8.10
ExecutablePath: /sbin/gpart
Package: gpart 0.1h-4.1
ProcAttrCurrent: unconfined
ProcCmdline: gpart /dev/sdh
ProcEnviron:
 SHELL=/bin/bash
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
 LANG=en_NZ.UTF-8
 LANGUAGE=en_NZ:en
Signal: 8
SourcePackage: gpart
Stacktrace:
 #0 0x0804d430 in ?? ()
 #1 0x0804b381 in ?? ()
 #2 0x0804be09 in ?? ()
 #3 0xb7ee5685 in __libc_start_main () from /lib/tls/i686/cmov/libc.so.6
 #4 0x08048d71 in ?? ()
StacktraceTop:
 ?? ()
 ?? ()
 ?? ()
 __libc_start_main () from /lib/tls/i686/cmov/libc.so.6
 ?? ()
Title: gpart crashed with SIGFPE in __libc_start_main()
Uname: Linux 2.6.27-3-generic i686
UserGroups:

Revision history for this message
StoatWblr (stoatwblr) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Symbolic stack trace

StacktraceTop:?? ()
?? ()
?? ()
__libc_start_main () from /lib/tls/i686/cmov/libc.so.6
?? ()

Revision history for this message
Apport retracing service (apport) wrote : Symbolic threaded stack trace
Revision history for this message
Pedro Villavicencio (pedro) wrote : Missing Backtrace

Thanks for your bug report. Please try to obtain a backtrace http://wiki.ubuntu.com/DebuggingProgramCrash and attach the file to the bug report. This will greatly help us in tracking down your problem.

Changed in gpart:
importance: Undecided → Medium
status: New → Incomplete
Revision history for this message
Pedro Villavicencio (pedro) wrote :

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to New. Thanks again!.

Changed in gpart:
status: Incomplete → Invalid
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.