From: Andrew Cagney <ac131313@redhat.com>
To: gdb-patches@sources.redhat.com
Subject: [rfa:doc] Clarify stabs @
Date: Thu, 30 Jan 2003 03:12:00 -0000 [thread overview]
Message-ID: <3E389829.9040104@redhat.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 45 bytes --]
Following up a very old e-mail.
Ok?
Andrew
[-- Attachment #2: diffs --]
[-- Type: text/plain, Size: 1405 bytes --]
2003-01-29 Andrew Cagney <ac131313@redhat.com>
* stabs.texinfo (Member Type Descriptor): Clarify description of
`@'. Suggested by Ben Hutchings.
Index: stabs.texinfo
===================================================================
RCS file: /cvs/src/src/gdb/doc/stabs.texinfo,v
retrieving revision 1.8
diff -u -r1.8 stabs.texinfo
--- stabs.texinfo 2 Jan 2003 14:36:48 -0000 1.8
+++ stabs.texinfo 30 Jan 2003 03:06:26 -0000
@@ -2724,11 +2724,22 @@
@node Member Type Descriptor
@section The @samp{@@} Type Descriptor
-The @samp{@@} type descriptor is for a member (class and variable) type.
-It is followed by type information for the offset basetype, a comma, and
-type information for the type of the field being pointed to. (FIXME:
-this is acknowledged to be gibberish. Can anyone say what really goes
-here?).
+The @samp{@@} type descriptor is used together with the @samp{*} type
+descriptor for a pointer-to-non-static-member-data type. It is followed
+by type information for the class (or union), a comma, and type
+information for the member data.
+
+The following C++ source:
+
+@smallexample
+typedef int A::*int_in_a;
+@end smallexample
+
+generates the following stab:
+
+@smallexample
+.stabs "int_in_a:t20=*21=@@19,1",128,0,0,0
+@end smallexample
Note that there is a conflict between this and type attributes
(@pxref{String Field}); both use type descriptor @samp{@@}.
next reply other threads:[~2003-01-30 3:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-30 3:12 Andrew Cagney [this message]
2003-01-30 8:03 ` Eli Zaretskii
2003-01-30 15:44 ` Andrew Cagney
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=3E389829.9040104@redhat.com \
--to=ac131313@redhat.com \
--cc=gdb-patches@sources.redhat.com \
/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