All program launches imply debugging in Eclipse 4.30 #1424
Description
I'm running the latest Wild Web Developer 1.3.3.202311211923 on Eclipse 4.30, which I've just upgraded. Following this switch from Eclipse 4.29 to 4.30 I had the unpleasant surprise too see that running a JS file is identical to debugging it. There's no difference between choosing "Run As" -> "Node program" and "Debug As" -> "Node program":
Combined with the fact that the debugging itself clears the program's output from the Console view and seemingly replaces it with debug tracing like
Debug server listening at ::1:35157
{
seq: 11,
type: 'response',
request_seq: 6,
command: 'threads',
success: true,
body: { threads: [ [Object] ] }
}
it's really annoying. There are actually two consoles, the one with the program's output is hidded by another containing the debug adapter output.
Activity
[-]All program launches imply debugging[/-][+]All program launches imply debugging in Eclipse 4.30[/+]mickaelistria commentedon Dec 7, 2023
Can you please open a separate issue about the fact that the DAP output console is shown by default? I don't think it's a behavior we want to keep.
[-]All program launches imply debugging in Eclipse 4.30[/-][+]All program launches imply debugging in Eclipse _4.30_[/+][-]All program launches imply debugging in Eclipse _4.30_[/-][+]All program launches imply debugging in Eclipse 4.30[/+]mickaelistria commentedon Dec 8, 2023
Have you identified whether there is a missing setting in the Debug Adapter configuration to skip debug?
acarstoiu commentedon Dec 8, 2023
Don't know where to check the defaults. Here is the settings tab for a configuration shown both for Run and for Debug:
Maybe the culprit is the "Monitor Debug Adapter launcher process" checkbox? If I check the "Override defaults and..." checkbox, it protests because of the empty "Command" field, upon running. I mean, I don't know what to put in there.
akurtakov commentedon Sep 23, 2026
Is this one still a problem?