Quoting Thomas Bushnell BSG <[EMAIL PROTECTED]>:
> Derek Atkins <[EMAIL PROTECTED]> writes:
>
> > And yes, this code has been there a long time, in order to detect a
> > double-free.
>
> That's a bug then; you can't access freed memory, period.
Well, yes and no...
> Indeed, it is fair game for an attempted read out of freed memory to
> fault; it's been freed, you can't read it. You have no right to
> assume that malloc/free even keep pages mapped after a free.
Agreed, and it would be a bug if the freed object was kept around. The fact
that the object-free function checks first is not a bug -- it's more of a
debugging tool. If the code actually segfaulted at _that_ point it would show
you that you have a bug elsewhere causing the freed object to be retained.
However the fact that we check for an invalid pointer and then, later, set the
object to an invalid pointer before freeing it is perfectly legal code.
> Thomas
-derek
--
Derek Atkins, SB '93 MIT EE, SM '95 MIT Media Laboratory
Member, MIT Student Information Processing Board (SIPB)
URL: http://web.mit.edu/warlord/ PP-ASEL-IA N1NWH
[EMAIL PROTECTED] PGP key available
_______________________________________________
gnucash-devel mailing list
gnucash-devel@gnucash.org
https://lists.gnucash.org/mailman/listinfo/gnucash-devel
