×
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.
Hi Vern,
Actually the SEP debugging does not require all that dancing - it just
worked for me, just like the other stuff - take another look - heh -
nothing like the green-screen way!
I don't understand. You told me that the way to set a SEP breakpoint
is to set the breakpoint in the program, then right-click it and change
it's properties to a SEP breakpoint. Right? Or did I misunderstand?
That's the only way I've found to set a SEP breakpoint.
That means that you have to *already* have the program in debug -- how
else would you set the breakpoint? So you already have it in debug
once. When someone calls that program, it opens up debug a second time
because the SEP breakpoint fires. So you have two debug sessions open
at the same time. You can't close the original one, because you'd lose
your SEP breakpoint. You have to have two open at once.
That's what I meant when I said it works like the green screen one. If
you use SEP in the green screen debugger it's the same ordeal. You open
a debug session to set the breakpoint, and leave it open. When the SEP
breakpoint fires, you have to open a second session and start debug
again on the SEP breakpoint. So you have to debug sessions open at once.
The GUI one is a little nicer than the green-screen in that it will
start the second debug session for you, whereas you have to type the
commands in the green screen one. But, to me, that's a minor difference.
In WDSC it's very different from that. You use the work with objects
tool to find your program, right-click it, and choose "Debug as Service
entry." No need to put the program into a debug session and keep the
session open. When the program is run, the debugger opens up
automatically, and you take it from there. Only one debug session open...
I agree that this debugger is so much nicer. And had just seen some
reference to starting it in iNav - nice. I asked the Rational folks at
COMMON Focus, IIRC, if the 2 debuggers use the same code - they do not.
They use completely different code on the PC side. On the server side,
they share some of the same code, they all use the same debugger APIs in
the operating system. Though, they have different server programs
(which, IMHO, is silly) so they must not use ALL of the same code...
midrange.com
