From:	Hans-Bernhard Broeker <broeker AT physik DOT rwth-aachen DOT de>
Newsgroups:	comp.os.msdos.djgpp
Subject:	Re: how to reduce virtual memory ?
Date:	18 Jul 2000 12:09:38 GMT
Organization:	Aachen University of Technology (RWTH)
Lines:	21
Message-ID:	<8l1he2$ii3$1@nets3.rz.RWTH-Aachen.DE>
References:	<8l1ffl$j08$1 AT front7 DOT grolier DOT fr>
NNTP-Posting-Host:	acp3bf.physik.rwth-aachen.de
Mime-Version:	1.0
X-Trace:	nets3.rz.RWTH-Aachen.DE 963922178 19011 137.226.32.75 (18 Jul 2000 12:09:38 GMT)
X-Complaints-To:	abuse AT rwth-aachen DOT de
NNTP-Posting-Date:	18 Jul 2000 12:09:38 GMT
Originator:	broeker@
To:	djgpp AT delorie DOT com
DJ-Gateway:	from newsgroup comp.os.msdos.djgpp
Reply-To:	djgpp AT delorie DOT com

"Sébastien Kirche" <seki AT club-internet DOT fr> wrote:

> I am trying to port an old graphical Borland C program to djgpp/grx.
> I manage to compile, but it crashes at run-time.
[...]
> Does someone got a clue, to reduce that amount, or to point what causes such
> an allocation ?

The typical reason for the crash would be incorrect porting of 16bit
code that used 'far pointers' and segment to DJGPP, which doesn't have
the former, and where protected mode requires big changes in the way
you handle the latter.

The problems in the debuggers are hard to analyse remotely without
seeing at least a minimal source code that tackles them. For now, you
could still use 'nm' output of your executable to locate the position
of the crash. 

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

- Raw text -