Filip SkokanandArchkon 2004fbd164 debugger: wait for target startup ...

The inspector can accept a connection before an --inspect-brk target
enters its frontend wait. Runtime.runIfWaitingForDebugger can then be
handled too early, allowing the target to subsequently block forever.

Wait for NodeRuntime.waitingForDebugger before initializing and
releasing launched targets. Race the handshake against disconnects and
apply it to both interactive and probe startup.

Refs: https://github.com/nodejs/node/issues/64116
Assisted-by: codex:gpt-5.6-sol
Co-authored-by: Archkon <180910180+Archkon@users.noreply.github.com>
Signed-off-by: Archkon <180910180+Archkon@users.noreply.github.com>
Signed-off-by: Filip Skokan <panva.ip@gmail.com>
PR-URL: https://github.com/nodejs/node/pull/65194
Reviewed-By: Trivikram Kamat <trivikr.dev@gmail.com>
Reviewed-By: James M Snell <jasnell@gmail.com>

2026-08-17 11:08:38 +03:00

..

inspect_client.js

debugger: add edit-free runtime expression probes to node inspect

2026-04-19 15:59:10 +00:00

inspect_helpers.js

debugger: wait for target startup

2026-08-17 11:08:38 +03:00

inspect_probe.js

debugger: wait for target startup

2026-08-17 11:08:38 +03:00

inspect_repl.js

debugger: wait for target startup

2026-08-17 11:08:38 +03:00

inspect.js

inspector: add --cond to node inspect probe mode

2026-07-13 17:00:51 +00:00