This is the mail archive of the
mailing list for the GDB project.
Re: BUG: MI reporting wrong attributes for casted variables
Nick Roberts wrote:
> Daniel Jacobowitz writes:
> > On Fri, Jun 22, 2007 at 08:17:39AM +1200, Nick Roberts wrote:
> > > Report it as a bug to the Eclipse CDT team. They have misinterpreted
> > > the meaning of the "editable" attribute.
> > >
> > > This has been reported at leasted once before, possibly by you (or at
> > > least another Sascha using Eclipse CDT) when I said:
> > And also by Vladimir, two years ago. What is the use of the current
> > "editable" attribute? I don't see anything in the manual that would
> > conflict with changing it.
> Actually looking at the manual, rather than the code, it looks like this
> might have been the intended meaning:
> The `-var-assign' Command
> -var-assign NAME EXPRESSION
> Assigns the value of EXPRESSION to the variable object specified by
> NAME. The object must be `editable'. If the variable's value is
I agree that currently, 'editable' is not particularly useful, and if 'editable'
means '-var-assign most likely will succeeed', it would be better.
> altered by the assign, the variable will show up in any subsequent
> `-var-update' list.
> So if you mean add this case to the existing ones, that seems reasonable.
> It would make redisplay faster if this field was added to the output
> of -var-create and -var-list-children. This is probably especially
> important for remote targets.
I'm not sure. Getting the 'editable' attribute does not require
talking to inferiour, so what target you use does not matter.