Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 260030 - sci-chemistry/gchempaint crash
Summary: sci-chemistry/gchempaint crash
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: AMD64 Linux
: High normal (vote)
Assignee: Jeffrey Gardner (RETIRED)
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-02-23 17:17 UTC by Giuseppe Marco Randazzo <zeld>
Modified: 2009-02-28 01:56 UTC (History)
2 users (show)

See Also:
Package list:
Runtime testing required: ---


Attachments
emerge --info (emergeinfo.txt,4.09 KB, text/plain)
2009-02-23 18:04 UTC, Giuseppe Marco Randazzo <zeld>
Details
more libtool compilation warning (emerge_gchempaint_warning.txt,5.14 KB, text/plain)
2009-02-23 18:09 UTC, Giuseppe Marco Randazzo <zeld>
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Giuseppe Marco Randazzo <zeld> 2009-02-23 17:17:42 UTC
Hi :-) when i try to start gchempaint i get a Segmentation Fault. This is the backtrace:

(no debugging symbols found)
...
...
[Thread debugging using libthread_db enabled]
(no debugging symbols found)
...
...
[New Thread 0x7f89d1540760 (LWP 4827)]
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7f89d1540760 (LWP 4827)]
0x00007f89ccb94680 in gconf_value_get_string () from /usr/lib/libgconf-2.so.4

I've an arch amd64, with glibc  2.9-r1 and gcc-4.3.2-r3

Thanks for helping :-)

Reproducible: Always
Comment 1 Reinis Danne 2009-02-23 17:33:15 UTC
Please add output of emerge --info

And your stack trace is useless without debugging symbols. Read this and add additional info:
http://www.gentoo.org/proj/en/qa/backtraces.xml

I'm on amd64 and using glibc-2.8_p20080602-r1 and have no such problem.
Comment 2 Giuseppe Marco Randazzo <zeld> 2009-02-23 18:04:53 UTC
Created attachment 182918 [details]
emerge --info

I've attached emerge --info and this is the backtrace with more output:

#0  0x00007ff41be8e680 in gconf_value_get_string () from /usr/lib/libgconf-2.so.4
#1  0x00007ff4201016ad in gcu::Application::Application () from /usr/lib/libgcu.so.0
#2  0x00007ff42057132a in gcpApplication::gcpApplication () from /usr/lib/libgchempaint-0.8.7.so
#3  0x0000000000402d49 in gcpStandaloneApp::gcpStandaloneApp ()
#4  0x0000000000402a19 in main ()

Thanks
Comment 3 Giuseppe Marco Randazzo <zeld> 2009-02-23 18:09:33 UTC
Created attachment 182922 [details]
more libtool compilation warning

i add some warning that i see when gchempaint compile. These are reported by libtool :|
Comment 4 Justin Lecher (RETIRED) gentoo-dev 2009-02-24 14:40:35 UTC
I cannot reproduce it on x86,

but get the same segfault on amd64.

Both tested with gcc-4.3 and glibc-2.8.
Comment 5 Jeffrey Gardner (RETIRED) gentoo-dev 2009-02-28 00:51:35 UTC
New version in portage fixes this.
Thanks!
je_fro
Comment 6 Giuseppe Marco Randazzo <zeld> 2009-02-28 01:56:33 UTC
Hi :) first of all thanks ;) but i've an other problem related to the update, but is rifered to gchemutils and i think is not appropriate post here, then i open an other bug report abount this :)

zeld