You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Setting an SEP on a program works fine until the program gets recompiled. After that, it's not possible to get the SEP to be triggered again. Removing and adding the SEP doesn't work either. Only restarting the Debug Service will make it work again...until the program gets recompiled.
RDi doesn't suffer from this because it includes an action to refresh the SEPs; this action must be run after a program is recompiled, and it works fine:
This action seems to be missing from the VS Code Debug Extension and should be added, IMHO.
The text was updated successfully, but these errors were encountered:
@sebjulliand I was so glad to see this issue - we have been running into it as well, and we couldn't figure out what was going on. It's puzzling though that removing and adding the SEP doesn't fix this either.
@sebjulliand This is a known missing feature. There is some amount of work to implement this feature in the debug service. We will try to add this feature in the next debug service update.
@mkwan01 Thanks for the update - this is a critical issue for our development team that prevents them from fully adopting VS Code for their IBM i work.
Debug extension: 2.0.2
Debug service: 2.0.1
Setting an SEP on a program works fine until the program gets recompiled. After that, it's not possible to get the SEP to be triggered again. Removing and adding the SEP doesn't work either. Only restarting the Debug Service will make it work again...until the program gets recompiled.
RDi doesn't suffer from this because it includes an action to refresh the SEPs; this action must be run after a program is recompiled, and it works fine:
This action seems to be missing from the VS Code Debug Extension and should be added, IMHO.
The text was updated successfully, but these errors were encountered: