Re: [cc65] memory corruption?

Date view Thread view Subject view

From: Groepaz (groepaz_at_gmx.net)
Date: 2003-06-03 14:26:19 

On Tuesday 03 June 2003 10:20, MagerValp wrote:
> >>>>> "UvB" == Ullrich von Bassewitz <uz_at_musoftware.de> writes:
>
> UvB> free() will add most blocks to the free list, which is a double
> UvB> linked list of free blocks. Links are stored inside the freed
> UvB> blocks. Any form of memory corruption may cause free() to enter
> UvB> an endless loop.
>
> OK, that sounds like what's happening.
>
> UvB> Your best chance is to look through the code for memory block
> UvB> overwrites. If I remember correctly, you had a special affinity
> UvB> for code like this:
>
> UvB>         struct x* X = malloc (sizeof (X));
>
> UvB> So I would look out for similar problems:-)
>
> Already checked for that :)
>
> UvB> Other possibility: If the code compiles&runs on a PC, use a
> UvB> malloc debugger on the PC.
>
> Yeah, I'm thinking that I should write a test program on the PC. Where
> can I find a malloc debugger and how does it work?

electric fence.... on a linux system, simply link -lefence

:)

gpz
----------------------------------------------------------------------
To unsubscribe from the list send mail to majordomo_at_musoftware.de with
the string "unsubscribe cc65" in the body(!) of the mail.

Date view Thread view Subject view

This archive was generated by hypermail 2.1.3 : 2003-06-03 14:28:49 CEST