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 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).. Thanks, Willett Kempton