Community
Participate
Working Groups
I'm unclear on what the Disconnect button of the debug view should exactly do? From what I'm seeing, it seems that BPs are uninstalled, suspended contexts are resumed, but the contexts remains attached (The agent context_detach() is not invoked). Should not it also detach from attached contexts? Thanks.
Hello, No update on this Bug: I just would like a clarification on what Disconnect is supposed to do: Should it detach the debugger from the attached contexts? Thanks for the clarification. Regards.
As a user, I care about the effects of the debugger on my target system: - Are there still any breakpoints ? - Does my program or system run any slower ? - Does the debug agent hog any memory on my target ? What are the effects on my target after a "disconnect" operation ? What is the effect of "being attached" ? If it's not noticeable to me as an end user, I don't care about it.
Currently, the agent does not do auto-detach on disconnect. If a client does "attach" then disconnects, the debuggee remains attached. The client can do "detach" next time it connects. Auto-detach seems a good thing to have. However, it can be a problem when multiple clients access same target. I’m not sure what is the best way to handle this.
> Auto-detach seems a good thing to have. However, it can be a problem when multiple clients access same target. I’m not sure what is the best way to handle this. I guess we can determine how many clients are connected? If yes, then what about auto-detaching on disconnect when only one client is connected?
