Mail Archives: djgpp/1997/11/14/06:16:21
On Sun, 09 Nov 1997 07:50:02 -0800 in comp.os.msdos.djgpp Ofer Corshid <oferco AT cs DOT huji DOT ac DOT il> wrote:
: Hye,
: Thanking anyone who will answer this:
: When I run my program (a big one, a makefile with 7
: implementation files), I get this unclear message:
: Exiting due to signal SIGSEGV
[snip]
: What should I do?
For full details you should read the FAQ, which explains a lot about
debugging your programs. Briefly:
Your program tried to do something it was not allowed to do, noticed
it, and shut itself down. The information it printed tells you what
went wrong. The main thing you'll want to do here is run the `symify'
program; pass it the filename of your executable as a parameter, while
the traceback above is still on the screen, and it will fill in next
to the `Call frame traceback EIPs' the function names they represent.
The traceback shows which functions were being processed at the time
of the crash; the topmost function is the deepest one in the tree.
If you linked your program with `-s', you'll now regret it; you won't
get any of this information. Relinking your program without the `-s'
switch but with the same other switches and then running symify will
work.
If you compiled your program with `-g' (and didn't link with `-s') you
will get more detailed information; specifically, each EIP will also
have its source filename and line number added as well as the function
name.
If after doing this you still have no idea what is going wrong, try
posting the complete symified traceback here, along with the code of
the function that crashed (the highest one in the list which is one of
yours, and not a libc function), identifying which line symify is
pointing to, and no doubt people will be able to help you.
--
Regards,
george DOT foot AT merton DOT oxford DOT ac DOT uk
- Raw text -