Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: "Eli Zaretskii" <eliz@is.elta.co.il>
To: Ben.Hutchings@Symbian.Com
Cc: gdb-patches@sources.redhat.com
Subject: Re: Fix for stabs documentation
Date: Tue, 22 Oct 2002 12:47:00 -0000	[thread overview]
Message-ID: <2427-Tue22Oct2002214941+0200-eliz@is.elta.co.il> (raw)
In-Reply-To: <OFEE1C61F1.E7DEFFC3-ON80256C5A.0038EA8B@intra> (Ben.Hutchings@Symbian.Com)

> From: Ben.Hutchings@Symbian.Com
> Date: Tue, 22 Oct 2002 11:43:01 +0100
> 
> This isn't really a patch, but I couldn't find any other contact
> address for "the gdb developers".
> 
> Section 7.8 of the stabs documentation (at
> http://sources.redhat.com/gdb/current/onlinedocs/stabs.html) says:
> 
>     The `@' 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?).
> 
> I suggest using something along the following lines:
> 
>     The `@' type descriptor is used together with the `*' 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:
> 
>         typedef int A::*int_in_a;
> 
>     generates the following stab:
> 
>         .stabs "int_in_a:t20=*21=@19,1",128,0,0,0

Thanks.  The change is okay with me, assuming it describes accurately
what `@' does (I don't know enough about stabs to tell).


      reply	other threads:[~2002-10-22 19:47 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-22  3:43 Ben.Hutchings
2002-10-22 12:47 ` Eli Zaretskii [this message]

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=2427-Tue22Oct2002214941+0200-eliz@is.elta.co.il \
    --to=eliz@is.elta.co.il \
    --cc=Ben.Hutchings@Symbian.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