Closed theres-waldo closed 3 years ago
To illustrate, compare the output of the same variable in the gdb view:
to the locals view:
Note also the gdb view puts in enumerator names, that's a nice touch.
This issue remains the primary reason I continue reaching for the gdb view. Running print localVar->mThis->mThat->mOtherThing
is just so much quicker than visually scanning the non-indented text blob in the Local Variables view for those members.
We're aware that traversing complex object graphs stills sucks. You can (as of a couple months ago) put localVar->mThis->mThat->mOtherThing
in the search bar to evaluate that expression without dropping into gdb though.
This has been revamped significantly and I'm going to call it finished. Please file new issues if you find additional things that annoy you.
While the little arrows help a bit, the contents of a local variable in the Local Variables view is still pretty hard to parse if the variable is a structure with fields that are themselves structures etc.
Pretty-printing the value the way gdb / rr does with
set print pretty on
would be a nice improvement.