Date: Wed, 12 Nov 1997 11:09:27 +0100 (GMT+0100)
From: Mrazek Petr <mrazek AT cas3 DOT zlin DOT vutbr DOT cz>
To: Paul Derbyshire <ao950 AT FreeNet DOT Carleton DOT CA>
cc: djgpp AT delorie DOT com
Subject: Re: Degugging large projects under RHIDE
In-Reply-To: <6467d1$dug@freenet-news.carleton.ca>
Message-ID: <Pine.LNX.3.91.971112110544.15443F-100000@cas3.zlin.vutbr.cz>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Precedence: bulk

> Thomas Demmer (demmer AT LSTM DOT Ruhr-UNI-Bochum DOT De) writes:
> > No, unless you have a typo here. 60kB x 8 are merely 256kB, something
> > that every computer nowadays should have free. FWIW, post what RHIDE
> > spits
> > out when you create a bug report.
> 
> Are you allocating that stuff on the stack in this project? Cause the
> stack has exactly that much space ... 256K. Be sure to allocate your 60K
> blocks on the heap.
> --
For first: my program tries to allocate exactly those buffers: 6414, 
2896, 4776, 2172, 10520, 13316, 200, 20000 and it's 60296 at all and then 
crashes. Maybe I have bad explaine it.
Second: malloc allocates always on the heap, doesn't it?

Petr Mrazek