×
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.
Buck,
I have set break points inside RDP while writing code.
That is part of the power of an I.D.D.E. Integrated Debug/Development Environment. I am using RDP 8.0.3. <Cool>
It does NOT get the check marked on top of the Blue-Circle, until I am actually inside Debug mode. Which is expected behavior.
It works that way in most other I.D.D.E too, like Visual Studio.
When I run into problems, I switch my debug-view over to *LISTING. That view seems to be ROCK-SOLID. Usually, I did a code change and forgot to check for a clean compile. That is why it is nice to flip to the *LISTING VIEW. But, I usually like using to use LPEX as my Debug Viewer.
And when I restart debug, it usually remembers my break points too!
<awesome> For repeative debugging, that is a life-saver! <Big Smile>
-Ken Killian-
-----Original Message-----
From: wdsci-l-bounces@xxxxxxxxxxxx [mailto:wdsci-l-bounces@xxxxxxxxxxxx] On Behalf Of Buck Calabro
Sent: Tuesday, March 05, 2013 1:13 PM
To: wdsci-l@xxxxxxxxxxxx
Subject: Re: [WDSCI-L] RDP Debug when STRDBG active
Don't try to set a breakpoint before beginning the debug.
midrange.com
