Confirmed users
496
edits
Remote Debugging Protocol: Difference between revisions
Jump to navigation
Jump to search
→Detaching From a Thread: Detaching loses breakpoints, etc.
(→Lexical Environment Examples: Remove outdated frame id property from example.) |
(→Detaching From a Thread: Detaching loses breakpoints, etc.) |
||
| Line 457: | Line 457: | ||
This indicates that the thread exited on its own before receiving the "detach" packet. The client should follow by sending a "release" packet; see [[#Exiting_Threads|Exiting Threads]], below. | This indicates that the thread exited on its own before receiving the "detach" packet. The client should follow by sending a "release" packet; see [[#Exiting_Threads|Exiting Threads]], below. | ||
Detaching from a thread causes all breakpoints, watchpoints, and other debugging-related state to be forgotten. | |||
If the client sends a <code>"detach"</code> packet to a thread that is not in the <b>Running</b>, <b>Paused</b>, or <b>Exited</b> state, the actor sends an error reply of the form: | If the client sends a <code>"detach"</code> packet to a thread that is not in the <b>Running</b>, <b>Paused</b>, or <b>Exited</b> state, the actor sends an error reply of the form: | ||