Follow-up Comment #2, bug #67722 (group gforth):

BTW, you may wonder about the fact that you get this message and a -262 throw
in this case.  That's a feature of glibc, which notices double free in some
cases and then writes the message and then abort()s; the resulting SIGABRT
leads to the -262 throw at the Forth level.  Other libc implementations do not
have this feature, and even in glibc it only works in some cases.  In other
cases when the address has been reused, a double free() or double fclose()
will happily free the newly allocated memory and/or corrupt the data there.


    _______________________________________________________

Reply to this item at:

  <https://savannah.gnu.org/bugs/?67722>

_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/

Attachment: signature.asc
Description: PGP signature

Reply via email to