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
Took a while to figure out that logpoints output simply goes to process(java process to debugged) output and not vscode's debug console as it's shown in docs. It'd be extremely helpful especially with remote debugging to get those logpoint messages back via debug protocol if that's possible.
Bump this old request as this will really be helpful when doing remote debugging.
When the logpoints message prints to stdout instead of vscode's debug console, it is much harder to find and track.
Another place to look is SetBreakpointsRequestHandler.java#L219. There is some code there to notify the user if an error occurred in the logpoint evaluation by sending a UserNotificationEvent. That event is picked up in TypeScript at extension.ts#L126. If there was no error, this code doesn't do anything.
I'm just guessing, but maybe a fix would be for JdtEvaluationProvider.logMessageToExpression() to generate an expression which returns the formatted log message, then SetBreakpointsRequestHandler.handleEvaluationResult() would extract the string and send it in a new kind of event, say a "logpoint" event. Then extension.ts would handle that event and write to the debug console.
Took a while to figure out that logpoints output simply goes to process(java process to debugged) output and not vscode's debug console as it's shown in docs. It'd be extremely helpful especially with remote debugging to get those logpoint messages back via debug protocol if that's possible.
If I'm right this
System.out
happens in this companion project JdtEvaluationProvider.java#L225The text was updated successfully, but these errors were encountered: