Ubuntu

gpartedbin crashed with SIGABRT in raise() during partition copying

Reported by Martin Spacek on 2011-04-29
22
This bug affects 3 people
Affects Status Importance Assigned to Milestone
gparted (Ubuntu)
Medium
Unassigned

Bug Description

Binary package hint: gparted

I was running from the final natty 64 bit livecd (on USB), trying to copy all of the partitions from my internal SATA drive to my external SATA drive via eSATA, on my Lenovo Thinkpad W510. This was a long operation. I left, and when I came back, gparted had apparently crashed (according to the little dialog box that natty popped up).

After inspecting the destination drive however, it seems all the partitions did copy. I'm not exactly sure when during the copying process gparted crashed.

ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: gparted 0.7.0-1ubuntu1
ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2
Uname: Linux 2.6.38-8-generic x86_64
Architecture: amd64
Date: Fri Apr 29 10:48:19 2011
ExecutablePath: /usr/sbin/gpartedbin
LiveMediaBuild: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1)
ProcCmdline: /usr/sbin/gpartedbin
ProcEnviron:
 LANGUAGE=en_US:en
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
Signal: 6
SourcePackage: gparted
StacktraceTop:
 raise () from /lib/x86_64-linux-gnu/libc.so.6
 abort () from /lib/x86_64-linux-gnu/libc.so.6
 ?? () from /lib/x86_64-linux-gnu/libc.so.6
 ?? () from /lib/x86_64-linux-gnu/libc.so.6
 ?? () from /lib/x86_64-linux-gnu/libc.so.6
Title: gpartedbin crashed with SIGABRT in raise()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

Martin Spacek (mspacek) wrote :
Martin Spacek (mspacek) wrote :

Actually, it looks like all the partitions except the swap partition were copied properly. So perhaps the crash occurred while trying to copy the swap partition. I've added a screenshots of my source and destination drives.

Martin Spacek (mspacek) wrote :
visibility: private → public

StacktraceTop:
 raise (sig=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:64
 abort () at abort.c:92
 __libc_message (do_abort=2, fmt=0x7f65c209f400 "*** glibc detected *** %s: %s: 0x%s ***\n") at ../sysdeps/unix/sysv/linux/libc_fatal.c:189
 malloc_printerr (action=3, str=0x7f65c209c707 "realloc(): invalid next size", ptr=<value optimized out>) at malloc.c:6283
 _int_realloc (av=0x7f65c22d91c0, oldp=0x1f8a460, oldsize=<value optimized out>, nb=144) at malloc.c:5238

Changed in gparted (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in gparted (Ubuntu):
status: New → Confirmed
dino99 (9d9) wrote :

Natty has reached EOL now. Is it still an issue ?

Changed in gparted (Ubuntu):
status: Confirmed → Incomplete
Launchpad Janitor (janitor) wrote :

[Expired for gparted (Ubuntu) because there has been no activity for 60 days.]

Changed in gparted (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers