Home | Docs | Forums | Lists | Bugs | Planet | Store | GMN | Get Gentoo!
Not eligible to see or edit group visibility for this bug.
View Bug Activity | Format For Printing | XML | Clone This Bug
zomps@zomps ~ $ gdb inkscape GNU gdb 6.6 Copyright (C) 2006 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "i686-pc-linux-gnu"... (no debugging symbols found) Using host libthread_db library "/lib/libthread_db.so.1". (gdb) run Starting program: /usr/bin/inkscape (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1225308496 (LWP 21075)] Program received signal SIGSEGV, Segmentation fault. [Switching to Thread -1225308496 (LWP 21075)] 0x083318b7 in ?? () (gdb) quit The program is running. Exit anyway? (y or n) y
that output is useless ... please review this document: http://www.gentoo.org/doc/en/bugzilla-howto.xml
I think this is a known bug in gcc-4.2. See: http://gcc.gnu.org/bugzilla/show_bug.cgi?id=30252#c22 Maybe adding -fno-strict-aliasing would help?
Yes, it helps, Thank you
we've got an upstream PR so re-open
this is actually the same bug as bug #179554.
thanks, i thought this was already filed *** This bug has been marked as a duplicate of bug 179554 ***
