Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
RE: [cdt-dev] Support for "target-detach" and "target-disconnect"

> -----Original Message-----
> From: cdt-dev-bounces@xxxxxxxxxxx 
> [mailto:cdt-dev-bounces@xxxxxxxxxxx] On Behalf Of Mikhail Khodjaiants
> Sent: April-14-10 1:59 PM
> To: cdt-dev@xxxxxxxxxxx
> Subject: Re: [cdt-dev] Support for "target-detach" and 
> "target-disconnect"
> On 14/04/2010 1:37 PM, Pawel Piech wrote:
> > I agree that an action is a heavy-weight solution here.  
> Could it be 
> > solved as a preference to the disconnect action behavior?  It could 
> > even bring up a dialog with a "remember my decision" option.
> > -Pawel
> Also "detach" can be applied to a process or or a thread group, 
> "disconnect" has no parameters.

Maybe the same action can be used for both behaviors?  We would
base ourselves on the debug context.

Currently, for DSF-GDB, the disconnect action does the following:
1- If a process (or one if its threads or frames) is selected, the 
action would do 'detach' of that process.  This is useful for
multi-process debugging.
2- If the launch is selected we exit gdb altogether

#2 is a duplication of what the terminate button does.
So, when the launch is selected, the terminate and disconnect
actions do the same thing.

How about making the disconnect action call 'disconnect' in this case?
Would that be enough for your use-case?


Back to the top