Re: Distributed Debugger after source changes/recompile

Hi Phil,

I just debugged a simple program (setting up a few breakpoints, stepping
through
a few conditions, etc.)
Then I introduces some source changes and recompiled my program.
The debugger came up and some of the breakpoints from the previous session
were missing which is expected as some lines all no longer were executable.
However, stepping was totally normal - it followed the logic as expected.

Then I made source changes, but did not recompile my code. Things became
quite messy. But usually you will see some executable lines colored in
black (as
non-executable) in such cases.

I was wondering if you could try using the STRDBG command in your example?
Let me know if you run into similar problem.

Thanks,
Vadim Berestetsky
Distributed Debugger Development
Internet:  berestet@ca.ibm.com


Phil Groschwitz <sublime78ska@yahoo.com>@midrange.com on 01/03/2002
09:04:42 AM

Please respond to code400-l@midrange.com

Sent by:  code400-l-admin@midrange.com


To:   code400-l@midrange.com
cc:
Subject:  Distributed Debugger after source changes/recompile


In the distributed debugger, after changing source
where lines are added and/or removed, the distributed
debugger is still using the prior version as far as
lines (source code is right, but when stepping it
doesn't step to the line you expect it to.)

I've gone into Application Preferences and Debug, and
deleted the profile for the pgm.  When going back in
all the breakpoints were gone but when I started debug
it still stepped on the wrong lines.

What do I have to do?  Do I need to end the STRCODE
server?  Signoff the STRCODE server?

Phil

__________________________________________________
Do You Yahoo!?
Send your FREE holiday greetings online!
http://greetings.yahoo.com
_______________________________________________
This is the CODE/400 Discussion & Support (CODE400-L) mailing list
To post a message email: CODE400-L@midrange.com
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/cgi-bin/listinfo/code400-l
or email: CODE400-L-request@midrange.com
Before posting, please take a moment to review the archives
at http://archive.midrange.com/code400-l.