https://sourceware.org/bugzilla/show_bug.cgi?id=27797
--- Comment #1 from Ahcheong Lee ---
Created attachment 13409
--> https://sourceware.org/bugzilla/attachment.cgi?id=13409&action=edit
crash test case
--
You are receiving this mail because:
You are on the CC list for the bug.
https://sourceware.org/bugzilla/show_bug.cgi?id=27797
--- Comment #2 from Ahcheong Lee ---
Sorry about the wrong comment
The crashed stack trace is
==14202==ERROR: AddressSanitizer: attempting double-free on 0x61900580 in
thread T0:
#0 0x5d809d in free (.../afl++/subjects_friend/size/si
https://sourceware.org/bugzilla/show_bug.cgi?id=27797
Nick Clifton changed:
What|Removed |Added
Status|UNCONFIRMED |ASSIGNED
Ever confirmed|0
https://sourceware.org/bugzilla/show_bug.cgi?id=27797
Nick Clifton changed:
What|Removed |Added
Resolution|--- |FIXED
Status|ASSIGNED
https://sourceware.org/bugzilla/show_bug.cgi?id=27797
--- Comment #3 from cvs-commit at gcc dot gnu.org ---
The master branch has been updated by Nick Clifton :
https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=6cb40a679b23b07b9fe0c43147d300b630deec70
commit 6cb40a679b23b07b9fe0c43147d
https://sourceware.org/bugzilla/show_bug.cgi?id=27797
Tom Tromey changed:
What|Removed |Added
CC||tromey at sourceware dot org
--- Comment
https://sourceware.org/bugzilla/show_bug.cgi?id=27797
--- Comment #6 from Nick Clifton ---
(In reply to Tom Tromey from comment #5)
Hi Tom,
> I think what realloc does when passed a 0 size is implementation-defined.
Ah - I did wonder about that.
> It may call free, but it may not. So, I thi
https://sourceware.org/bugzilla/show_bug.cgi?id=27797
--- Comment #7 from Mark Wielaard ---
realloc with size zero is super confusing, so much so that C11 deprecated the
use of calling realloc with size zero:
http://www.open-std.org/jtc1/sc22/wg14/www/docs/summary.htm#dr_400
--
You are receivin
https://sourceware.org/bugzilla/show_bug.cgi?id=27797
--- Comment #8 from Tom Tromey ---
> Personally I am not too worried about memory leaks. There are quite a
> few of them still in the sources, but I do not see why they get raised
> as issues from tiemn to time. None of the binutils tools a