After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 158219 - SEGV on startup
SEGV on startup
Status: RESOLVED DUPLICATE of bug 157871
Product: gparted
Classification: Other
Component: application
0.0.x
Other Linux
: Normal normal
: ---
Assigned To: gparted maintainers alias
gparted maintainers alias
Depends on:
Blocks:
 
 
Reported: 2004-11-13 22:45 UTC by Geoffrey Leach
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Geoffrey Leach 2004-11-13 22:45:54 UTC 
launch gparted.  No messages output.  This does not appear to be a dup of   	
157871.  Reproducable with parted-1.6.16.

From gdb
Starting program: /usr/local/src/gparted/src/gparted
Reading symbols from shared object read from target memory...done.
Loaded system supplied DSO at 0xffffe000
[Thread debugging using libthread_db enabled]
[New Thread -1211866464 (LWP 3380)]
 
Program received signal SIGSEGV, Segmentation fault.

+ Trace 51959

Thread NaN (LWP 3380)

  • #0 GParted::Win_GParted::init_device_info
    at stl_vector.h line 501
  • #1 Win_GParted
    at Win_GParted.cc line 64
  • #2 main
    at main.cc line 41 

Debugging with ddd/gdb, although the trace shows init_device_info(), a
breakpoint in that function does not work.  From that, and the fact that
stl_vector.h is in /usr/include/g++-3/, I suspect that what we have here is a
constructor problem in init_device_info().  I'm running g++ (GCC) 3.3.3 20040412
(Red Hat Linux 3.3.3-7)
Comment 1 Plors (Bart H) 2004-11-14 18:44:17 UTC 
afaics this is a dup of 157871.
Please try the latest CVS or better yet, wait for gparted 0.0.7 which will be
released shortly.

*** This bug has been marked as a duplicate of 157871 ***