Bug 597644 - [abrt] crash in eclipse-platform-1:3.5.2-1.fc13: Process /usr/lib/eclipse/eclipse was killed by signal 6 (SIGABRT)
Summary: [abrt] crash in eclipse-platform-1:3.5.2-1.fc13: Process /usr/lib/eclipse/ecl...
Alias: None
Product: Fedora
Classification: Fedora
Component: eclipse
Version: 13
Hardware: i686
OS: Linux
Target Milestone: ---
Assignee: Andrew Overholt
QA Contact: Fedora Extras Quality Assurance
Whiteboard: abrt_hash:435ae15d9bc2b430e3881654c6d...
Depends On:
TreeView+ depends on / blocked
Reported: 2010-05-29 23:11 UTC by Mads Kiilerich
Modified: 2010-08-24 22:29 UTC (History)
6 users (show)

Clone Of:
Last Closed: 2010-08-24 22:29:37 UTC

Attachments (Terms of Use)
File: backtrace (21.50 KB, text/plain)
2010-05-29 23:11 UTC, Mads Kiilerich
no flags Details
new crash - new backtrace (140.45 KB, text/plain)
2010-06-04 15:43 UTC, Mads Kiilerich
no flags Details

Description Mads Kiilerich 2010-05-29 23:11:35 UTC
abrt 1.1.1 detected a crash.

architecture: i686
Attached file: backtrace
cmdline: /usr/lib/eclipse/eclipse
component: eclipse
executable: /usr/lib/eclipse/eclipse
global_uuid: 435ae15d9bc2b430e3881654c6d698833de48ead
package: eclipse-platform-1:3.5.2-1.fc13
rating: 4
reason: Process /usr/lib/eclipse/eclipse was killed by signal 6 (SIGABRT)
release: Fedora release 13 (Goddard)

How to reproduce
Eclipse just crashed.
It seems like this backtrace doesn't say much:
abort() with "warning: can't find linker symbol for virtual table for `(null)' value"
some fatal error was detected "*** glibc detected *** %s: %s: 0x%s ***\n"

Comment 1 Mads Kiilerich 2010-05-29 23:11:38 UTC
Created attachment 417939 [details]
File: backtrace

Comment 2 Mads Kiilerich 2010-06-04 15:43:36 UTC
Created attachment 421273 [details]
new crash - new backtrace

I got something similar again. This time abrt rejected to report it (for strange reasons).

This was on another machine, but probably with the same CDT project.

Comment 3 Andrew Overholt 2010-08-23 19:29:49 UTC
Hi Mads.  Can you provide the CDT project for debugging purposes?

Comment 4 Mads Kiilerich 2010-08-23 22:58:35 UTC
Sorry, I don't remember which project it was. But probably nothing fancy; probably just some existing autotools-based project which I somehow tricked CDT to consider an autotool project.

I haven't seen it since.

I now consider it very likely that it is a duplicate of https://bugzilla.redhat.com/buglist.cgi?quicksearch=+invalid+fastbin+entry and has been fixed in glibc?

Comment 5 Andrew Overholt 2010-08-24 22:29:37 UTC
Thanks, Mads.  I'm not sure about that glibc issue but if you haven't seen it recently, I'll close this.

Note You need to log in before you can comment on or make changes to this bug.