This is the mail archive of the
gdb@sourceware.org
mailing list for the GDB project.
meaning of tags in output
- From: Markus Teich <markus dot teich at stusta dot mhn dot de>
- To: gdb at sourceware dot org
- Date: Fri, 19 Apr 2013 08:57:54 +0200
- Subject: meaning of tags in output
Hello,
i found that some expressions give extra tags in the output when
printed. Unfortunately i did not find any documentation about them, so i
looked in the source and tried to summarize them myself.
Is there already a documented list?
Since i am only working with C-Code right now, i tried to filter, which
tags are relevant for C and which are not.
Can you help me complete/correct the list?
--Markus
<synthetic pointer>
if "this" is not used in a C++ member function it is an synthetic pointer.
irrelevant for C.
<repeats %u times>
can be omitted with 'set print elements 0'
<invalid address>
seems to be only used for Pascal and C++ source.
<error reading variable>
occurs, when a variable is printed which is not yet initialized. Is it
C++ only?
<address of value unknown>
???seems to be for errorhandling in gdb???
<internal function %s>
???
<incomplete sequence %WHATEV>
seems to only occur, when gdb interprets something as a wchar array and
finds a "half" wchar.
<unavailable>
???
<Error reading address %HEX?: %s>
could not read adress. What is the difference to the next tag?
<Address %HEX out of bounds>
Memory access on BADFOOD pointer
<invalid float value>
google hints: could be serious (stack corruption?).
<incomplete type>
occurs if e.g. type is a struct without members.
<optimized out>
compiler optimizations.