|
I have spent a good part of this morning helping a co-worker debug a series of programs and subprocedures in service programs. We set a SEP on the entry program and call it. All is good at this point. We step into the code. Still good until we get to the first call to a subprocedure. When we step into it, we get a screen telling us that the source cannot be found. It has three buttons. If we select the button for the compile listing, it works fine, but each time through in debug is the same way. If we select the button to find the source and browse to the correct, modified source in her development library, It opens the source but always enters the subprocedure source at the wrong line. Actually, it is not even in the correct subprocedure. We have cleared the WDSc cache, removed all SEP's, stopped and restarted the debug server and recompiled / recreated all programs and service programs, including the modules, after confirming the development library is at the top of the library list. Also, we can debug this same series of programs from the GS (STRDBG) without any problems. What am I missing? Kyle
As an Amazon Associate we earn from qualifying purchases.
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.