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


  • Subject: Re: Strange debug problem
  • From: "Mauricio Della-Quercia" <mauriciodq@xxxxxxxxxxx>
  • Date: Wed, 13 Oct 1999 14:42:10 EDT

[SNIP]

>However, neither setting breakpoints within the module nor attempting to
>step into it with F22 appears to work: the program blithely carries on
>to the line after the CALLB.  There are no error messages in the joblog.
>
>The program's behaviour would imply that the code in the module in
>question is _not_ actually being executed.
>
>I've spent a lot of time in the ILE debugger, and I've never seen it
>behave like this.  Does anyone have any ideas?


I've had this happen to me a few times when the program was compiled with 
Optimize Level set to other than *NONE.

I would suggest that the module in question be recompiled making sure that 
the optimize level is set to *NONE.

Hope this helps.

Mauricio Della-Quercia



______________________________________________________
Get Your Private, Free Email at http://www.hotmail.com
+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---

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.