× 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. MIDRANGE-L
  3. May 2003

Odd Debug behavior

I just encountered some very odd debug behavior  on V4R5 ...

I'm debugging a very large CL program ... 1500 lines.

I compiled the CL and then brought it up in debug ... I tried to set a
breakpoint at line 1430.  The debugger reported that it set a breakpoint at
line 897!

I then tried to set a breakpoint at line 1440 ... it still set the
breakpoint at line 897.

If I set the breakpoint at line 895, it was set properly.

Basically, anytime I set a breakpoint at a line higher than 897, the
breakpoint was actually set at line 897.

I dug a bit more and changing compile options & setting breakpoints ... when
I removed the ALWRTVSRC(*NO), the breakpoint was set correctly.

Has anyone ever experienced this before?

I had placed a call with IBM ... there is no PTF available for this, but I
think they are going to put out a KB article.

david

-- 
David Gibbs
david@xxxxxxxxxxxx

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