× 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. WDSCI-L
  3. March 2008

Re: Debugging Blues

dnitke wrote:
Program A calls Program B
Program C calls Program B
Program D calls Program B --- want to debug this call

2. Adding new programs to a run in WDSCi debugger doesnt seem to work. Take the above scenerio; I then thought hey I will start debugging Program D and add Program B afterwards because if I add it from the get go it will catch the first call and I'm screwed. So I start the debug with only Program D. Hit F6 to the call then change the properties to add Program B, hit F6 and the program never comes up like 5250 showing the source until the actual abend occurs (problem I'm fixing) which is way into the processing of the program.

If I follow your meaning, a workaround would be to set a breakpoint on the call to Program B from program D, then when you hit that breakpoint to a 'step into' to start debugging program B.

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.