× 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.


  1.  Home
  2. RPG400-L
  3. January 2006

Re: Debugging Problem

Hi Mike,
 
<snip>
I have a weird problem. I am not sure how to even really describe this. I
have a program with 33 internal subprocedures. I call OpenNIBTCursor. The
debugger hits line one of the procedure, then hits line 1 of
OpenStockholdersEquityCursor, which is MANY lines down in the code. As far
as I can tell, I have everything setup correctly. Are there any bugs like
this? We are on V5R3 with the latest CUME (just installed last night). This
happens with both STRDBG and the WDSc debugger.
<snip>
 
I had a problem when recompiling an interactive program, and then debugging
it - only to find that I am debugging the original program (copied to
QRPLOBJ) and looking at the new source. Schoolboy error, but we all do it
sometimes. :-)
 
Could it be something as basic as that? Probably not, but it's worth a try -
what is the library your debugged program is in - it shoud display on-screen
when debugging via STRDBG. Is the program in the library you expect..?
 
Cheers
 
Larry

As an Amazon Associate we earn from qualifying purchases.

This thread ...
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.