From:	firewind <firewind AT metroid DOT dyn DOT ml DOT org>
Newsgroups:	comp.os.msdos.djgpp
Subject:	Re: Can't understand error codes
Date:	10 Oct 1997 02:37:09 GMT
Organization:	Netcom
Lines:	37
Message-ID:	<61k4cl$8nt@sjx-ixn3.ix.netcom.com>
References:	<343D85F9 DOT 446B AT jcu DOT edu DOT au>
NNTP-Posting-Host:	elp-tx3-21.ix.netcom.com
Mime-Version:	1.0
To:	djgpp AT delorie DOT com
DJ-Gateway:	from newsgroup comp.os.msdos.djgpp

Oon Lin <Oon DOT Lin AT jcu DOT edu DOT au> wrote:
> Hi !

> Can anyone tell me where can I get information on the various error
> codes that DJGPP spits out ? I'm new to DJGPP and every time there's an
> error message or a warning during build , I can't seem to understand it. 

Huh? I've found only a very few, very rare warnings\errors that gcc spits
out that are unintelligible. Can you give some examples?

> I had been trying to fix up things by trial and error and I don't seem
> to be doing a good job at it.

> And how do I find out the meaning to words like SIGABRT or SIGSEGV ? 

SIGABRT = abort signal. This is raised when the abort() function is called, I
suppose.

SIGSEGV = segmentation violation. This is raised when you access memory that
is not allocated to your program. (This is a very rough and inaccurate
definition, sorry.)

> And
> what's all the stuff I get when the program crashes ? It looks like they
> are the  values in the different registers . How can I know what does
> that mean so that I can debug ??

This traceback and how to interpret it is -clearly- explained in the FAQ,
section 9.2.

hth.

-- 
[- 				 firewind	                            -]
[-   email: firewind AT metroid DOT dyn DOT ml DOT org (home), firewind AT aurdev DOT com (work)  -]
[- 	    "You're just jealous because the voices talk to -me-."          -]
[-                   Have a good day, and enjoy your C.		            -]

- Raw text -