Message-Id: <3.0.16.19971127175345.1dd79e4c@hem1.passagen.se>
Date: Thu, 27 Nov 1997 17:53:48 -0500
To: gaggi AT dulcamara DOT cs DOT unibo DOT it (Nicola Gaggi)
From: Peter Palotas <blizzar AT hem1 DOT passagen DOT se>
Subject: Re: malloc() bug?
Cc: djgpp AT delorie DOT com
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Precedence: bulk

At 10.31 1997-11-27 GMT, you wrote:
>Hi,
>
>I am wondering if anyone out there has had the same problem:
>I am writing a program that need to dinamically allocate a huge number of
>little buffers (about 10 bytes each), but I have run into problem with
>malloc(), i receive SIGSEGV inside the malloc() code. 
>The program code seems correct, and anyway it is not particularly
>complicate, it only performs some allocation and copy, so what it can be?
>Every malloc'ed pointer is free'ed up correctly. 
>Is it a bug of malloc() function? Any suggestion? 

Please post the smallest code that reproduces this problem. 

-- Peter Palotas alias Blizzar -- blizzar AT hem1 DOT passagen DOT se --

*****************************************************
* A brief description of DJGPP:                     *
* NEVER BEFORE HAS SO FEW DONE SO MUCH FOR SO MANY! *
*****************************************************