I understand that the recommended thing to do after a rebuild of the program would be go to the SEP view, select the SEP of interest and click the refresh button.
Mike
---
Mike Hockings, M.Eng.
IBM Rational Developer for System z and Power Systems Software Technical Support
IBM Canada Ltd. Laboratory
hockings@xxxxxxxxxx
voice 1-905-413-3199 T/L 313-3199 ITN 23133199
From: WDSCI-L <wdsci-l-bounces@xxxxxxxxxxxxxxxxxx> on behalf of Therrien, Paul via WDSCI-L <wdsci-l@xxxxxxxxxxxxxxxxxx>
Date: Wednesday, October 19, 2022 at 11:18
To: Rational Developer for IBM i <wdsci-l@xxxxxxxxxxxxxxxxxx>
Cc: Therrien, Paul <ptherrien@xxxxxxxxxxx>
Subject: [EXTERNAL] [WDSCI-L] RDI Debug - SEP stops working
When debugging in RDi I find that at times the SEP stops working and RDi will not jump into debug when I execute my program.
This happens when I debug by setting an SEP, run the program, then make some changes, then remove the SEP, then re-add the SEP.
I can do this multiple times, but then at some point RDI stops intercepting the program execution.
My only solution to fixing this has been to shutdown RDi and restart.
Is there a better solution? Is there a way to reset the SEP?
Paul
--
This is the Rational Developer for IBM i (WDSCI-L) mailing list
To post a message email: WDSCI-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit:
https://lists.midrange.com/mailman/listinfo/wdsci-l
or email: WDSCI-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at
https://archive.midrange.com/wdsci-l .
Help support midrange.com by shopping at amazon.com with our affiliate
link:
https://amazon.midrange.com
midrange.com
