abrt 1.1.1 detected a crash.
Attached file: backtrace
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"
Created attachment 417939 [details]
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.
Hi Mads. Can you provide the CDT project for debugging purposes?
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?
Thanks, Mads. I'm not sure about that glibc issue but if you haven't seen it recently, I'll close this.