From: Markus Teich <markus.teich@stusta.mhn.de>
To: gdb@sourceware.org
Subject: meaning of tags in output
Date: Fri, 19 Apr 2013 06:58:00 -0000 [thread overview]
Message-ID: <5170EAF2.3060007@stusta.mhn.de> (raw)
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.
next reply other threads:[~2013-04-19 6:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-19 6:58 Markus Teich [this message]
2013-04-23 18:17 ` Tom Tromey
2013-04-23 18:53 ` Markus Teich
2013-04-24 19:09 ` Tom Tromey
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5170EAF2.3060007@stusta.mhn.de \
--to=markus.teich@stusta.mhn.de \
--cc=gdb@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox