www.delorie.com/archives/browse.cgi   search  
Mail Archives: djgpp/1996/03/27/10:57:42

Date: Wed, 27 Mar 1996 17:48:48 +0200 (IST)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
To: "J. Springthorpe" <juy AT le DOT ac DOT uk>
Cc: djgpp AT delorie DOT com
Subject: Re: Exiting due to signal SIGSEGV?
In-Reply-To: <4j8iir$29@falcon.le.ac.uk>
Message-Id: <Pine.SUN.3.91.960327173531.4844M-100000@is>
Mime-Version: 1.0

On 26 Mar 1996, J. Springthorpe wrote:

> Please, please help. I'm in a big time rush. I've read the FAQ v2, but I get
> lost with all the technical jargon. I'm a newbie to C++, and don't know much

It's usually bad idea to try to learn an entirely new environment while  
``in a big time rush''.

> but usually it crashes big time. I run DOS from Windows, and have tried
> installing csdpmilb.zip (DPMI server). I can only get feedback from g032-v2

If you run under Windows, you don't need CWSDPMI.  DJGPP programs will 
use the DPMI services of Windows.

> DMPI memory available: a tad over 4Mb
> DPMI swap space available: 0

That's way too few.  With the PIF editor (it's in the `Main' program 
group) open the file `dosprmpt.pif' and set the maximum memory size for 
both Extended and Expanded memory to -1, then save the file and try 
again.  You should see much more memory now reported by go32-v2.  If you 
still have the crashes (btw, do you mind telling more about what exactly 
crashes and how?), check in the Control panel (also in the `Main' group) 
how large is your swap file, and enlarge it to be at least 20MB.

> Anyway, my source code complies fine, but when tring to run I get the message;
> 
> Exiting due to signal SIGSEGV
> General Protection Fault at (lots of numbers etc)

That most probably means that your program has a bug (like dereferencing a
NULL pointer, writing outside your address space, etc.) Section 9.2 in the
FAQ (a node called `Crash traceback', if you read the hypertext Info
version of the FAQ) tells how to use the `symify' program to convert the
(lots of numbers) into a human-readable stack trace that will tell you at
what line in what source file did the problem happen.  You should then
debug your program at that point. 

- Raw text -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019