On Wed, Oct 20, 2010 at 07:59:27PM +0100, Nicholas Marriott wrote:
I like it a lot.
Although I don't see much point in NBBY :-).
Couldn't you print the failing pointer on the other realloc messages? I
guess it may not be much use.
I'm sorry, but I don't get you here.
Otherwise reads
On Thu, Oct 21, 2010 at 10:06:23AM +0200, Otto Moerbeek wrote:
On Wed, Oct 20, 2010 at 07:59:27PM +0100, Nicholas Marriott wrote:
I like it a lot.
Although I don't see much point in NBBY :-).
Couldn't you print the failing pointer on the other realloc messages? I
guess it may not
On Thu, Oct 21, 2010 at 10:06:23AM +0200, Otto Moerbeek wrote:
On Wed, Oct 20, 2010 at 07:59:27PM +0100, Nicholas Marriott wrote:
I like it a lot.
Although I don't see much point in NBBY :-).
Couldn't you print the failing pointer on the other realloc messages? I
guess it may not
On Wed, Oct 20, 2010 at 09:27:50AM +0200, Otto Moerbeek wrote:
Hi,
when feeding free(3) or realloc(3) a bogus or already free pointer, it
helps to see the actual pointer. So here's a diff to do that.
Typical output:
a.out in free(): error: bogus pointer (double free?)
I like it a lot.
Although I don't see much point in NBBY :-).
Couldn't you print the failing pointer on the other realloc messages? I
guess it may not be much use.
Otherwise reads fine and works for me.
On Wed, Oct 20, 2010 at 09:27:50AM +0200, Otto Moerbeek wrote:
Hi,
when feeding
