From: brennan AT news DOT rt66 DOT com (Brennan "The Rev. Bas" Underwood)
Newsgroups: comp.os.msdos.djgpp
Subject: Re: DJGPP vs Borland C++
Date: 1 Feb 1997 20:36:46 -0700
Organization: Acid Brain
Lines: 27
Distribution: world
Message-ID: <5d124e$rqi$1@mack.rt66.com>
References: <Pine DOT SUN DOT 3 DOT 91 DOT 970127082529 DOT 7773G-100000 AT is>
NNTP-Posting-Host: mack.rt66.com
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp

In article <Pine DOT SUN DOT 3 DOT 91 DOT 970127082529 DOT 7773G-100000 AT is>,
Eli Zaretskii  <eliz AT is DOT elta DOT co DOT il> wrote:
>
>On Mon, 27 Jan 1997, Linley Henzell wrote:
>
>> Well, I'm having some problems with a C program written with Borland C++
>> 3.1 which refuses to work with DJGPP v2. It compiles fine, but every
>> time I run it, it aborts with a SIGSEGV GPF. I have no idea why this
>> happens, because it seems to choose a completely arbitrary point at
>> which to abort (I checked with Symify), and my program contains nothing
>> which I can imagine being objectionable (like pointers or dynamic memory
>> allocation).
>> Meanwhile, a little test program works okay with DJGPP.
>
>I suggest a printf debugging session.  Insert printf statements into your 
>program until you see where does it crash.  It's amazing how sometimes 
>this age-old technique can put you back on track.

Also, don't compile with -O or -fomit-frame-pointer if you want a coherent
stack traceback.


Brennan
-- 
 brennan AT rt66 DOT com |  static char msg[]="Bill Gates is the Anti-christ.";
Riomhchlaraitheoir|  Add this message to every program you write! I do!
   Rasterfarian   |  <http://brennan.home.ml.org>                          -O