http://sourceware.org/bugzilla/show_bug.cgi?id=14007
--- Comment #8 from Markus Trippelsdorf <markus at trippelsdorf dot de> 2012-04-22 21:36:35 UTC --- (In reply to comment #7) > > That said, I actually looked at the backtrace, and I see this: > > > #3 0x0000000000571ee1 in gold::Symbol_table::add_from_pluginobj<64, false> > (this=0x7fffffff7f60, obj=0x3afaef90, name=0x0, ver=0x0, > sym=0x7fffffff7940) at > /var/tmp/portage/sys-devel/binutils-9999/work/binutils/gold/symtab.cc:1340 > #4 0x0000000000534f80 in gold::Sized_pluginobj<64, false>::do_add_symbols > (this=0x3afaef90, symtab=0x7fffffff7f60, layout=0x7fffffff81c0) > at > /var/tmp/portage/sys-devel/binutils-9999/work/binutils/gold/plugin.cc:1074 > > The fact that name == NULL in the call to add_from_pluginobj very strongly > suggests that this is a bug in the plugin. The plugin is trying to add a > symbol with a NULL name. That makes no sense and is leading directly to the > crash. Indeed. All I was trying to suggest is that perhaps there is a possibility for a better response, besides crashing, when gold is fed with garbage from an plugin. -- Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug. _______________________________________________ bug-binutils mailing list bug-binutils@gnu.org https://lists.gnu.org/mailman/listinfo/bug-binutils
