In message <[EMAIL PROTECTED]>, "Chris Ptacek" w
rites:
>I am getting a warning from a program I wrote:
>
>lined in free(): warning: chunk is already free.
>
>Is there anyway I can figure out where exactly this is happening, maybe
>cause a core or something.
ln -s A /etc/malloc.conf
This is happening in a call to free() ;; the memory being freed is either
not actually allocated or is somewhere that your programs memory does not
contain (ie address out of range).
Use mxgdb, ddd, or gdb to show all things things and step through the
executiong.
***
On Mon, Aug 14, 2000 at 02:10:16PM -0700, Chris Ptacek wrote:
> I am getting a warning from a program I wrote:
>
> lined in free(): warning: chunk is already free.
>
> Is there anyway I can figure out where exactly this is happening, maybe
> cause a core or something.
>From 'man free', which yo
In the last episode (Aug 14), Chris Ptacek said:
> I am getting a warning from a program I wrote:
>
> lined in free(): warning: chunk is already free.
>
> Is there anyway I can figure out where exactly this is happening, maybe
> cause a core or something.
Man malloc, see the "DEBUGGING MALLOC P
4 matches
Mail list logo
