traceback

[Adriaan van Os]

willett wrote:

> I'm using  gpc version 20051116, based on gcc-3.4.5.  Impressive 
> update!
>
> It is very nice to have the runtime error detection.  But of course it 
> means some new errors have to be dealt with, one way or another.  An 
> old program of mine is now getting...
>
> out of range (error #300 at 2c57)
>                                                                        
>                                   Trace/BPT trap

Assuming Mac OS X. Don't you get a crash report dialog ?

> Trying to get a less cryptic error report, maybe one with the 
> procedure stack at point of error, I compile as:
>
>    gp -mtraceback=full  progname
>
> But this does not add anything to the information in the out of range 
> error.  Also, it would be nice to have a list
> of error messages, so that error #300 could be looked up.
>
> Any thought on how to access more information for runtime errors?  
> (like a simple traceback of procedure calls)..

Try the following:

* add debug information to your program (by adding -g to the 
compilation options)
* have a look at the crash logs with /Applications/Utilities/Console

I am not sure if -mtraceback does anything for gpc (or gcc) on darwin.

Regards,

Adriaan van Os