Re: bad free()s in string.t

2004-07-08 Thread Leopold Toetsch
Nicholas Clark wrote: If I build parrot with --gc=libc on OS X I see some warnings about bad pointers being passed to free(). It's happening in a call from dod.c: #ifdef GC_IS_MALLOC /* free allocated space at (int*)bufstart - 1, * but not if it is used COW

bad free()s in string.t

2004-07-08 Thread Nicholas Clark
If I build parrot with --gc=libc on OS X I see some warnings about bad pointers being passed to free(). It's happening in a call from dod.c: #ifdef GC_IS_MALLOC /* free allocated space at (int*)bufstart - 1, * but not if it is used COW or external