Date:	Fri, 10 Oct 1997 16:53:28 -0700 (PDT)
Message-Id:	<199710102353.QAA03247@adit.ap.net>
Mime-Version:	1.0
To:	Oon Lin <Oon DOT Lin AT jcu DOT edu DOT au>, djgpp AT delorie DOT com
From:	Nate Eldredge <eldredge AT ap DOT net>
Subject:	Re: Can't understand error codes

At 11:33  10/10/1997 +1000, Oon Lin 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. 
>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.
You mean the GCC compiler? No, there isn't any documentation on the errors.
Most of them, IMHO, are at least somewhat self-explanatory. The bad ones
like "parse error" usually require to manually look over the code in the
area it mentions and check for syntax errors.
>And how do I find out the meaning to words like SIGABRT or SIGSEGV ? 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 ??
The libc documentation for `signal' tells what the signal names mean. That
"stuff" after a crash is a traceback. If you have compiled with `-g',
running `symify myprog.exe' after the crash will give you the functions and
line numbers in which the crash occured.
>
>Lastly , is it possible to have a pointer to a real mode function in
>DJGPP ? (Like a pointer to VESA 1.2's bank swicthing function ?) How do
>I get a pointer to it ?
Not directly, no. But you can use
__dpmi_simulate_real_mode_procedure_retf(). Look at its docs.

Nate Eldredge
eldredge AT ap DOT net

- Raw text -