|
From: Steve F. <sf...@re...> - 2004-12-09 18:23:28
|
Nicholas Nethercote wrote: > On Wed, 8 Dec 2004, Tom Hughes wrote: > >>> I get the above message. Now 0 bytes AFTER how should I interpret >>> it. 0 after is for me the last alloced byte to it should be ok, no? >> >> >> No, zero bytes after is the first byte after the block. If you imagine >> that you have a pointer to the end of the block and then add that >> number of bytes to it then that gives you the pointer through which >> your program was trying to read/write. > > > I wonder if that message should be changed to say 1 byte after -- enough > people get confused by this that it could be worthwhile. But then figuring out the address is kind of weird. How about "bad stuff happened at byte offset 0 after an allocation of size..." or "bad stuff happened at byte offset 0 into the range following an allocation of size..." "bad stuff happened at byte offset 0 into the range just after an allocation of size..." "bad stuff happened at byte offset 0 after the end of an allocation of size..." |