Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
* Fix for stabs documentation
@ 2002-10-22  3:43 Ben.Hutchings
  2002-10-22 12:47 ` Eli Zaretskii
  0 siblings, 1 reply; 2+ messages in thread
From: Ben.Hutchings @ 2002-10-22  3:43 UTC (permalink / raw)
  To: gdb-patches

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

Ben.


**********************************************************************
Symbian Ltd is a company registered in England and Wales with registered number 01796587 and registered office at 19 Harcourt Street, London, W1H 4HF, UK.
This message is intended only for use by the named addressee and may contain privileged and/or confidential information. If you are not the named addressee you should not disseminate, copy or take any action in reliance on it. If you have received this message in error please notify postmaster@symbian.com and delete the message and any attachments accompanying it immediately. Symbian does not accept liability for any corruption, interception, amendment, tampering or viruses occuring to this message in transit or for any message sent by its employees which is not in compliance with Symbian corporate policy.
**********************************************************************


^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: Fix for stabs documentation
  2002-10-22  3:43 Fix for stabs documentation Ben.Hutchings
@ 2002-10-22 12:47 ` Eli Zaretskii
  0 siblings, 0 replies; 2+ messages in thread
From: Eli Zaretskii @ 2002-10-22 12:47 UTC (permalink / raw)
  To: Ben.Hutchings; +Cc: gdb-patches

> 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).


^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2002-10-22 19:47 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2002-10-22  3:43 Fix for stabs documentation Ben.Hutchings
2002-10-22 12:47 ` Eli Zaretskii

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox