Date:	Wed, 9 Jun 1999 18:01:01 +0200
From:	Hans-Bernhard Broeker <broeker AT physik DOT rwth-aachen DOT de>
Message-Id:	<199906091601.SAA27466@acp3bf.physik.rwth-aachen.de>
To:	djgpp AT delorie DOT com
Subject:	Re: malloc() problem
Newsgroups:	comp.os.msdos.djgpp
Organization:	RWTH Aachen, III. physikalisches Institut B
X-Newsreader:	TIN [version 1.2 PL2]
Reply-To:	djgpp AT delorie DOT com

In article <v01540b01b383d83a2ae0@[145.18.167.138]> you wrote:
[...]

> used without calling CWSDPMI externally first, do work. My only remaining
> idea for the cause of this problem is that malloc simply won't do anything
> as "large" as 34K 

34K is nowhere even remotely 'large', by standards of the DJGPP
compiler and library. 34M yes, that'd be a bit large, but I'd still
expect it to work, without any problems.

> If anyone has some real-life source that does this and does work,
> preferably ANSI C, but C++ will do as well, I would be much obliged.

You're thinking the wrong way round, I think. You won't probably gain
anything from looking at other people's source, here: malloc() works,
and has been working, for all of us, for years on end.  So the problem
is not that your code is missing some magic cookie you might have to
grab from other programs.

It'd be way more helpful if you could prune down your failing program
to a small but _complete_ source code that still fails on your setup,
and post that, along with every bit of system information you can get
at (config.sys, autoexec.bat, 'set' output, and all that), so people
could check what may be going wrong, in your code.


--
Hans-Bernhard Broeker (broeker AT physik DOT rwth-aachen DOT de)
Even if all the snow were burnt, ashes would remain.

- Raw text -