Skip to content

node inspect restart prints Debugging/For-help message twice #39272

Description

@Trott
  • Version: 16.x.x
  • Platform: macOS
  • Subsystem: debugger

What steps will reproduce the bug?

$ node inspect test/fixtures/debugger/three-lines.js 
< Debugger listening on ws://127.0.0.1:9229/b7e232ed-227e-4482-864d-e58a37e4bc94
< 
< For help, see: https://nodejs.org/en/docs/inspector
< 
< Debugger attached.
< 
 ok
Break on start in test/fixtures/debugger/three-lines.js:1
> 1 let x = 1;
  2 x = x + 1;
  3 module.exports = x;
debug> restart
< Debugger listening on ws://127.0.0.1:9229/b7e232ed-227e-4482-864d-e58a37e4bc94
< For help, see: https://nodejs.org/en/docs/inspector
< 
< Debugger listening on ws://127.0.0.1:9229/d0c753b1-e93a-48e5-8323-df845d308bcd
< For help, see: https://nodejs.org/en/docs/inspector
< 
connecting to 127.0.0.1:9229 ... ok
< Debugger attached.
< 
Break on start in test/fixtures/debugger/three-lines.js:1
> 1 let x = 1;
  2 x = x + 1;
  3 module.exports = x;
debug> 

How often does it reproduce? Is there a required condition?

Every time.

What is the expected behavior?

After issuing restart in the debugger CLI, it will only print "Debugger listening on...For help..." message once.

What do you see instead?

It repeats the initial message from the start of the session, then issues the correct second message.

Additional information

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    debuggerIssues and PRs related to the Node.js command-line debugger.

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions