× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



I had a program fail & I "D"umped it. The reported dump shows the calling
procedure as what failed, but what really failed was a line of called that
is in another proc, that is called from the proc that the dump reported,
not very helpful.

What do I need to change so that it would have reported the line of code
that actually caused the failure?

In the below example the dump would report DoSomething as the failing line,
but really it was in the proc NextThing.

Dou %Eof(x);
Read x;
If Not %Eof(x);
DoSomething();
Endif;
Enddo;

Dcl-proc DoSomething;
NextThing();
End-proc;

Dcl-proc NextThing;
Actual failing line of code;
End-proc;

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.