https://sourceware.org/bugzilla/show_bug.cgi?id=20932
--- Comment #7 from Nick Clifton <nickc at redhat dot com> --- Hi Alan, > Nick, we really shouldn't ever get a warning symbol there. The testcase > object contains a fuzzed symbol table that has global symbols with an empty > string for their name. I reckon such symbols should not be allowed and I > think it would make more sense to error closer to the cause of the problem > rather than on one of the symptoms. Fair enough - please go ahead with your fix. I think that my patch should remain however, possibly with a changed error message, as I am not a fan of calls to abort() inside a library. In my opinion a library call should never end up with a seg-fault if it is possible to return to the caller with an error condition set. Even for something that is never expected to happen. Cheers Nick PS. I was finally able to reproduce the problem, but only with a toolchain configured for an i686-pc-inux-gnu target rather than x86_64-pc-linux-gnu. -- 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
