GNOME Bugzilla – Bug 157871
gparted 0.0.6 segfaults on start
Last modified: 2005-12-30 14:40:00 UTC
It's probably not reproducable. But all i have to do is start gparted to get the error: "Can't have a partition outside the disk" and it segfaults. I must add that i use a serillel (ata to sata) converter so i use a ide device as /dev/sda. gdb output: (gdb) run Starting program: /root/gparted/gparted-0.0.6/gparted/src/gparted warning: Unable to find dynamic linker breakpoint function. GDB will be unable to debug shared library initializers and track explicitly loaded dynamic code. [Thread debugging using libthread_db enabled] [New Thread 16384 (LWP 4126)] (gparted:4126): Gdk-WARNING **: locale not supported by Xlib (gparted:4126): Gdk-WARNING **: can not set locale modifiers Can't have a partition outside the disk! --------------------------- Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 16384 (LWP 4126)] GParted::Win_GParted::init_device_info() (this=0xbfffec50) at stl_vector.h:501 501 operator[](size_type __n) { return *(begin() + __n); }
What locale do you use? I recently fixed a crasher with some locales, although i can't see how dutch could pose a problem. Some suggestions: - set your locale to C ( export LANG=C ) - try the latest version from CVS and tell me if gparted still crashes.
Could you also tell me what version of (lib)parted you're using?
With 'export lang=C' i just get: Can't have a partition outside the disk! --------------------------- Segmentation fault I use parted-1.6.15 from Gentoo and it's patched by Gentoo. I don't think i'll test the cvs version, i'll be happy to test a new release though.
*** Bug 158219 has been marked as a duplicate of this bug. ***
What locale do you use? i forgot, it's: nl_NL@euro. I put it in my .bashrc and get a "locale not supported" error with pretty much everything i start so that shouldn't be a problem.
it doesn't matter, because you already tried it with LANG=C (btw, shouldn't you use nl_NL.UTF-8 ? )
Good news :) A friend who lives in the same town as i do experienced the same crasher at startup! This means i'm finally able to investigate this bug in person. Saturday is the big day, so expect a fix in CVS shortly after :)
That seems good news indeed. When it's fixed, could you mail me (or point me to) an up-to-date tar.bz2? Maybe now i can finally fix my partition table! :)
i'm sorry dudes, It appeared to be another bug, introduced in one of the latest CVS versions. So.. this one is still open.. :/
did anything chance with gparted-0.0.7 ? ( i dont think so, but who knows ;) )
Is any of the 'victims' still following this one? If so, please try with gparted-0.0.7 and gparted-0.0.8
root@mtranch[10]->src/gparted *** glibc detected *** malloc(): memory corruption (fast): 0x0880c438 *** Aborted root@mtranch[11]->rpm -q glib glib-1.2.10-15
Hi could you please provide some more information? - Backtrace would be cool ;) - version of gparted and libparted Did you built it yourself or did you use some binary package? thanks :)
Starting program: /usr/local/src/gparted-0.0.8/src/gparted [Thread debugging using libthread_db enabled] [New Thread -151034176 (LWP 30181)] Detaching after fork from child process 30195. Detaching after fork from child process 30197. Detaching after fork from child process 30199. Detaching after fork from child process 30201. Detaching after fork from child process 30203. Detaching after fork from child process 30205. Detaching after fork from child process 30207. Detaching after fork from child process 30209. Detaching after fork from child process 30211. Detaching after fork from child process 30213. Detaching after fork from child process 30215. Detaching after fork from child process 30217. Detaching after fork from child process 30219. Detaching after fork from child process 30221. Detaching after fork from child process 30223. Detaching after fork from child process 30225. Detaching after fork from child process 30227. Detaching after fork from child process 30229. Detaching after fork from child process 30231. Detaching after fork from child process 30233. Detaching after fork from child process 30235. Detaching after fork from child process 30237. *** glibc detected *** malloc(): memory corruption (fast): 0x081a5450 *** Program received signal SIGABRT, Aborted.
+ Trace 53788
Thread NaN (LWP 30181)
gparted-0.0.8 parted-1.6.15-5 ldd gparted libparted-1.6.so.12 => /usr/lib/libparted-1.6.so.12 (0x00719000) libgthread-2.0.so.0 => /usr/lib/libgthread-2.0.so.0 (0x00427000) libgtkmm-2.4.so.1 => /usr/local/stow/gtkmm/lib/libgtkmm-2.4.so.1 (0x00b2b000) libgdkmm-2.4.so.1 => /usr/local/stow/gtkmm/lib/libgdkmm-2.4.so.1 (0x001ae000) libatkmm-1.6.so.1 => /usr/local/stow/gtkmm/lib/libatkmm-1.6.so.1 (0x00111000) libgtk-x11-2.0.so.0 => /usr/lib/libgtk-x11-2.0.so.0 (0x00761000) libpangomm-1.4.so.1 => /usr/local/stow/gtkmm/lib/libpangomm-1.4.so.1 (0x00200000) libglibmm-2.4.so.1 => /usr/local/stow/glibmm/lib/libglibmm-2.4.so.1 (0x00150000) libsigc-2.0.so.0 => /usr/local/stow/libsigc++/lib/libsigc-2.0.so.0 (0x00191000) libgdk-x11-2.0.so.0 => /usr/lib/libgdk-x11-2.0.so.0 (0x00221000) libatk-1.0.so.0 => /usr/lib/libatk-1.0.so.0 (0x00dad000) libgdk_pixbuf-2.0.so.0 => /usr/lib/libgdk_pixbuf-2.0.so.0 (0x00197000) libpangoxft-1.0.so.0 => /usr/lib/libpangoxft-1.0.so.0 (0x00a7c000) libpangox-1.0.so.0 => /usr/lib/libpangox-1.0.so.0 (0x00a6f000) libpango-1.0.so.0 => /usr/lib/libpango-1.0.so.0 (0x00a2c000) libgobject-2.0.so.0 => /usr/lib/libgobject-2.0.so.0 (0x0028d000) libgmodule-2.0.so.0 => /usr/lib/libgmodule-2.0.so.0 (0x001ec000) libglib-2.0.so.0 => /usr/lib/libglib-2.0.so.0 (0x002c9000) libdl.so.2 => /lib/libdl.so.2 (0x001ef000) libuuid.so.1 => /lib/libuuid.so.1 (0x00714000) libstdc++.so.6 => /usr/lib/libstdc++.so.6 (0x07a4f000) libm.so.6 => /lib/tls/libm.so.6 (0x00344000) libgcc_s.so.1 => /lib/libgcc_s.so.1 (0x00591000) libc.so.6 => /lib/tls/libc.so.6 (0x005e8000) libpthread.so.0 => /lib/tls/libpthread.so.0 (0x00367000) libstdc++.so.5 => /usr/lib/libstdc++.so.5 (0x0042b000) libX11.so.6 => /usr/X11R6/lib/libX11.so.6 (0x00dc7000) libXrandr.so.2 => /usr/X11R6/lib/libXrandr.so.2 (0x00da8000) libXi.so.6 => /usr/X11R6/lib/libXi.so.6 (0x001f3000) libXinerama.so.1 => /usr/X11R6/lib/libXinerama.so.1 (0x001fb000) libXft.so.2 => /usr/X11R6/lib/libXft.so.2 (0x00379000) libfreetype.so.6 => /usr/lib/libfreetype.so.6 (0x0038b000) libfontconfig.so.1 => /usr/lib/libfontconfig.so.1 (0x003f2000) libXcursor.so.1 => /usr/X11R6/lib/libXcursor.so.1 (0x00a64000) libXrender.so.1 => /usr/X11R6/lib/libXrender.so.1 (0x00418000) libXext.so.6 => /usr/X11R6/lib/libXext.so.6 (0x004e7000) libpangoft2-1.0.so.0 => /usr/lib/libpangoft2-1.0.so.0 (0x004f5000) /lib/ld-linux.so.2 (0x005cf000) libexpat.so.0 => /usr/lib/libexpat.so.0 (0x0051b000) libz.so.1 => /usr/lib/libz.so.1 (0x0053a000)
thanks, that was quite usefull :) what's your locale btw?
LANG=en_US
hi Geofrey, i have to admit i'm a bit at a loss here.. It looks like something goes wrong while comparing two strings, but i've never seen a program crash on something like that. Maybe you could drop by in #gparted at irc.gimp.net sometime? That way we can do some 'live' debugging and track down the exact origin of the seg. Merry Christmas :)
its almost a year already, gparted is still broken LANG=nl_BE.UTF-8 LC_CTYPE="nl_BE.UTF-8" LC_NUMERIC="nl_BE.UTF-8" LC_TIME="nl_BE.UTF-8" LC_COLLATE="nl_BE.UTF-8" LC_MONETARY="nl_BE.UTF-8" LC_MESSAGES="nl_BE.UTF-8" LC_PAPER="nl_BE.UTF-8" LC_NAME="nl_BE.UTF-8" LC_ADDRESS="nl_BE.UTF-8" LC_TELEPHONE="nl_BE.UTF-8" LC_MEASUREMENT="nl_BE.UTF-8" LC_IDENTIFICATION="nl_BE.UTF-8" Version : gparted-0.0.8+cvs2005061901 Ref : http://bugzilla.ubuntu.com/show_bug.cgi?id=14266 <snip>.. write(3, "5\30\4\0\0\1\340\1I\0\340\1\267\1\24\0\233\4\5\0\1\1\340"..., 192) = 192 ioctl(3, FIONREAD, [0]) = 0 poll([{fd=4, events=POLLIN}, {fd=3, events=POLLIN}], 2, 0) = 0 nanosleep({0, 10000000}, 0) = ? ERESTART_RESTARTBLOCK (To be restarted) +++ killed by SIGSEGV +++
I guess this one can be closed. I reformatted my hd and everything's been great since then. It was a once in a million f*ck up, i don't think this will happen ever again :) Closed.
Hmmz, after some debugging i've concluded this crash is due to some problems in the <a href='http://www.cs.aau.dk/~olau/compose/'>String composition library</a> i use to format translatable strings with numbers in it. I'm writing a patch which i'll send to the author.
ok, 'fixed' in CVS. I'll contact the author of this library to discuss the matter, since i'm not sure about the correct way to handle this problem. In the meantime, i'd appreciate it if you guys would test the latest CVS version. thnx
Ofcourse i'm willing to test the latest Gparted, but like i said, my complete environment has changed. I used to run Gentoo, it's now Ubuntu Hoary with a complete new partitiontable. Now cfdisk doesn't complain anymore too, it was just something i've done back then...
Although i've temporarely 'fixed' this issue in GParted, the real problem still exists. I've filed a bug about it here: http://gcc.gnu.org/bugzilla/show_bug.cgi?id=23953
fixed in gcc-4.0.3 (http://gcc.gnu.org/bugzilla/show_bug.cgi?id=23953#c8) I'll still leave the workaround in gparted till gcc4 is more widely used.