Attached diff should solve the problem.
> -----Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > Sent: 10 May 2001 12:45 > To: [EMAIL PROTECTED] > Subject: cvs commit: apr/test testmem.c > > > dreid 01/05/10 03:45:04 > > Modified: test testmem.c > Log: > This adds Sanders suggestion of testing the reset for the > tracking memory > system. This also exposes a problem in that code where free is > called twice > for the same piece of memory, generating a segfault. Using > some extra debugging > This is what I see... > > Tracking Memory > Creating the memory area............................OK > Creating 10 lumps of memory, each 1024 bytes........OK > Writing to the lumps of memory......................OK > Check what we wrote.................................OK > About to reset the tracking memory.................. > calling free on 800259a8 > calling free on 80025598 > calling free on 80025598 > > I don't have tim to investigate in more detail at the moment. > > NB this will segfault, but it's being committed to allow people to > see the problem themselves :) > > Submitted by: Sander Striker <[EMAIL PROTECTED]> > Reviewed by: David Reid <[EMAIL PROTECTED]>
apr_memory.patch
Description: Binary data
