On Sun, Sep 03, 2023 at 09:30:49AM +0200, Otto Moerbeek wrote:
> > You can also be set upon a wrong foot: if an out of bounds write on a
> > adjacent chunk happens and lands in (another) free chunk, upon
> > allocation of that free chunk it will be reported as a "write after
> > free" case. It might even be that an allocation that was never
> > allocated and never freed is still "write after free" because of
> > "close" out of bounds writes.
> >
> > I'm thinking how to change the error message to reflect that.
I was thinking to change the message to "write to unallocated chunk",
trying to get the message trough that it also applies to chunks never
allocated but written to, not only to chunks that were freed and then
written to.
-Otto
