Re: [cdt-dev] Edit read/write access attributes for watchpoints

["Tepavich, Scott" <scott.tepavich@xxxxxxxxxxxxx>]

Thank you Mikhail, I was assuming as much (hence the question).  I’ve tried implementing my own FieldEditorFactory, which works well on the editing page; however, it duplicates the entries when creating a new watchpoint.  I can take the next step in defining a way to disable my contribution, when creating a new watchpoint, but this does not seem very clean.  Another approach could be to remove the common read/write access FieldEditors, and leave it up to the  underlying framework/implementation to define when to add these options; however, I’m likewise assuming this is not preferable.

 

I’m sure these are not the only FieldEditors that fall into this category/issue.  Any insight into a longer term solution for this type of problem would be greatly appreciated.

 

Thank you for your time –

Scott

 

 

From: cdt-dev-bounces@xxxxxxxxxxx [mailto:cdt-dev-bounces@xxxxxxxxxxx] On Behalf Of Mikhail Khodjaiants
Sent: Wednesday, October 31, 2012 10:36 AM
To: cdt-dev@xxxxxxxxxxx
Subject: Re: [cdt-dev] Edit read/write access attributes for watchpoints

 

On 31/10/2012 1:09 PM, Tepavich, Scott wrote:

Currently it is possible to set the read/write access attributes for a newly defined watchpoint; however, it is not possible to edit these attributes after it has been created.  I would like to add this capability for our TCF based debugger, but wanted to check if there is an environment in which this type of action should be prohibited.

None of the currently active CDT debugger implementations supports editing of the read/write attributes of watchpoints. The reason is GDB has different commands for each of the access types. It is possible to adjust the current implementations but it is not trivial.