This repository has been archived by the owner on Feb 1, 2022. It is now read-only.
Support for conditional breakpoints #68
Comments
|
It looks like a condition is already supported as the third parameter to |
2 tasks
Trott
pushed a commit
to Trott/io.js
that referenced
this issue
Oct 29, 2020
The `node-inspect` debugging client supports passing an optional third parameter as a string to be evaluated when the breakpoint is hit. If the condition evaluates to `true` in the current context, the breakpoint pauses execution; otherwise the execution continues. This was raised as an issue in nodejs/node-inspect#68, but the client already supports that functionality, so I thought it'd be helpful to add it to the node documentation. PR-URL: nodejs#35823 Reviewed-By: Rich Trott <[email protected]> Reviewed-By: Jan Krems <[email protected]>
targos
pushed a commit
to nodejs/node
that referenced
this issue
Nov 3, 2020
The `node-inspect` debugging client supports passing an optional third parameter as a string to be evaluated when the breakpoint is hit. If the condition evaluates to `true` in the current context, the breakpoint pauses execution; otherwise the execution continues. This was raised as an issue in nodejs/node-inspect#68, but the client already supports that functionality, so I thought it'd be helpful to add it to the node documentation. PR-URL: #35823 Reviewed-By: Rich Trott <[email protected]> Reviewed-By: Jan Krems <[email protected]>
BethGriggs
pushed a commit
to nodejs/node
that referenced
this issue
Dec 8, 2020
The `node-inspect` debugging client supports passing an optional third parameter as a string to be evaluated when the breakpoint is hit. If the condition evaluates to `true` in the current context, the breakpoint pauses execution; otherwise the execution continues. This was raised as an issue in nodejs/node-inspect#68, but the client already supports that functionality, so I thought it'd be helpful to add it to the node documentation. PR-URL: #35823 Reviewed-By: Rich Trott <[email protected]> Reviewed-By: Jan Krems <[email protected]>
BethGriggs
pushed a commit
to nodejs/node
that referenced
this issue
Dec 10, 2020
The `node-inspect` debugging client supports passing an optional third parameter as a string to be evaluated when the breakpoint is hit. If the condition evaluates to `true` in the current context, the breakpoint pauses execution; otherwise the execution continues. This was raised as an issue in nodejs/node-inspect#68, but the client already supports that functionality, so I thought it'd be helpful to add it to the node documentation. PR-URL: #35823 Reviewed-By: Rich Trott <[email protected]> Reviewed-By: Jan Krems <[email protected]>
BethGriggs
pushed a commit
to nodejs/node
that referenced
this issue
Dec 15, 2020
The `node-inspect` debugging client supports passing an optional third parameter as a string to be evaluated when the breakpoint is hit. If the condition evaluates to `true` in the current context, the breakpoint pauses execution; otherwise the execution continues. This was raised as an issue in nodejs/node-inspect#68, but the client already supports that functionality, so I thought it'd be helpful to add it to the node documentation. PR-URL: #35823 Reviewed-By: Rich Trott <[email protected]> Reviewed-By: Jan Krems <[email protected]>
|
It seems like this can be closed, but if I'm mistaken about that, please comment. Thanks. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I would love to see support for conditional breakpoints. I know the typical advise would be to use a more full-featured debugger, but I vastly prefer the command line debugging experience to having to tab over the chrome.
The text was updated successfully, but these errors were encountered: