I tried the -gl and it works this will be a big help.
thank you very much
JY
Jonas Maebe wrote:
On 25 Aug 2008, at 04:37, John Youngquist wrote:
When you enable things like range checking. How do you identify
when an exception has occurred and what it means?
Compile the program w
John Youngquist wrote:
>
> When you enable things like range checking. How do you identify
> when an exception has occurred and what it means?
>
AFAIK a checking code is generated for every error-possible code. That's why
it seems a little slower when you compile programs with checkings enabled
On 25 Aug 2008, at 04:37, John Youngquist wrote:
When you enable things like range checking. How do you identify
when an exception has occurred and what it means?
Compile the program with -gl (and all of its units with -g or -gl) to
see source information next to the addresses. If that does
When you enable things like range checking. How do you identify
when an exception has occurred and what it means?
I see messages like "Unhandled exception occurred at $hex address"
then a bunch more $hex address'
I don't know what to do with these numbers.
JY
__
