This is the mail archive of the
gdb-prs@sourceware.org
mailing list for the GDB project.
[Bug symtab/22365] "info locals" on an unitialized yet vector causes long garbage print
- From: "palves at redhat dot com" <sourceware-bugzilla at sourceware dot org>
- To: gdb-prs at sourceware dot org
- Date: Mon, 30 Oct 2017 12:05:50 +0000
- Subject: [Bug symtab/22365] "info locals" on an unitialized yet vector causes long garbage print
- Auto-submitted: auto-generated
- References: <bug-22365-4717@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=22365
Pedro Alves <palves at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |palves at redhat dot com
--- Comment #2 from Pedro Alves <palves at redhat dot com> ---
> OTOH, protection against printing unitialized values can be useful, so I
> consider not closing it. Feel free to deal with this report in any way.
There's no way for GDB to know whether the value was initialized or not. Also,
printing an uninitialized value is really no different from printing a value
that was initialized but has meanwhile been corrupted. gdb and pretty printers
must be robust against either case.
--
You are receiving this mail because:
You are on the CC list for the bug.