Date: Wed, 21 Jan 1998 15:38:40 -0800 (PST)
Message-Id: <199801212338.PAA05714@adit.ap.net>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
To: Cam <chafer AT elv DOT enic DOT fr>, djgpp AT delorie DOT com
From: Nate Eldredge <eldredge AT ap DOT net>
Subject: Re: 'Call Frame TraceBack'  Plz help a rookie !
Precedence: bulk

At 02:34  1/21/1998 +0100, Cam wrote:
>Hi
>Please, excuse my stupid question (and my english), but i've a pbm under 
>Rhide v1.4 and djgpp 2.0 with a c++ program.
>
>When compiling, no problem, but at running time, I always get the same 
>message : Call Frame Traceback from Rhide.
This is the message issued when your program does something illegal, i.e. it
has a bug. Some actions which are errors are not caught by real-mode
compilers. The error reporting mechanism is called a `signal', and is a
feature of ANSI C. You should see a signal name in your message, something
like SIG<something>. It would have been nice to have given the entire text
of the message. Here are the causes of the most common signals.

SIGSEGV
 Invalid memory reference. Perhaps you are dereferencing a NULL pointer,
overruning a pointer, or accessing unallocated memory.

SIGFPE
 Math error. Division by zero, sqrt(negative), etc.

SIGABRT
 Abort. Issued if you call `abort' or fail an `assert'.

SIGINT
 Interrupt. Issued if you hit Ctrl-C or Ctrl-Break.

The numbers underneath are a traceback. They can tell you where your program
was when it crashed. If you compile with debugging enabled, running the
`symify' program on this output will turn the numbers into the associated
function names. Section 9.2 of the DJGPP FAQ
(ftp://ftp.simtel.net/pub/simtelnet/gnu/djgpp/v2/faq210b.zip) explains how
to do this.

Nate Eldredge
eldredge AT ap DOT net