Bug 10683 - Optionally drop "member access control" level in MI -var-list-children output
Summary: Optionally drop "member access control" level in MI -var-list-children output
Status: NEW
Alias: None
Product: gdb
Classification: Unclassified
Component: varobj (show other bugs)
Version: unknown
: P2 enhancement
Target Milestone: 6.8
Assignee: Not yet assigned to anyone
URL:
Keywords: mi3
Depends on:
Blocks:
 
Reported: 2009-09-22 07:07 UTC by Andre'
Modified: 2023-08-31 17:22 UTC (History)
5 users (show)

See Also:
Host:
Target:
Build:
Last reconfirmed: 2011-11-10 00:00:00


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Andre' 2009-09-22 07:07:27 UTC
It would be nice if there were a way to (optionally) drop the artificial
'public/protected/private' levels that -var-list-children creates, as this would
help to reduce the number of round trips between a frontend and gdb.

One solution might be a new option:

  -var-list-children --all-values --no-member-access  <varname>

The left out values might even get re-added to the individual items such that
the result looks like

 
^done,numchild="1",children=[child={name="foo",exp="foo",numchild="1",value="{...}",type="Foo",access="protected"}]
Comment 1 Tom Tromey 2023-08-31 17:22:24 UTC
FWIW I have never understood this decision in MI.
It seems plainly bad.  If the access control is interesting,
it ought to be an attribute of the field, not some kind
of synthetic field-like thing.