[Bug gdb/31463] Artificial variables in locals output

["tromey at sourceware dot org" <sourceware-bugzilla@sourceware.org>]

https://sourceware.org/bugzilla/show_bug.cgi?id=31463

Tom Tromey <tromey at sourceware dot org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |tromey at sourceware dot org

--- Comment #2 from Tom Tromey <tromey at sourceware dot org> ---
(In reply to Dmitry Neverov from comment #1)

> I don't know if range-loop variables are shown by design or not.

Normally gdb just does what the compiler tells it.

Ada is a bit special because it emits some forms of debuginfo
via symbol names.  By default there isn't much of this any
more, but there are still a few cases that can't be avoided.

It would be fine by me to give Python a way to detect artificiality.
Omitting artificial variables via some option would also be fine.

I suppose my view is that, overall, seeing these isn't too confusing,
and might be helpful in some cases when debugging.  It lets you
inspect a compiler transform and see some objects that would otherwise
be inaccessible -- like if you want to debug some iterator implementation.

-- 
You are receiving this mail because:
You are on the CC list for the bug.