From: Daniel Jacobowitz <drow@mvista.com>
To: gdb-patches@sources.redhat.com
Subject: Re: [drow-cplus-branch] v3 destructors
Date: Fri, 01 Nov 2002 08:43:00 -0000 [thread overview]
Message-ID: <20021101164427.GA9014@nevyn.them.org> (raw)
In-Reply-To: <20021101163729.GA7955@nevyn.them.org>
On Fri, Nov 01, 2002 at 11:37:29AM -0500, Daniel Jacobowitz wrote:
> I've now added code to the stabs reader to report destructor field names
> properly. This changes get_destructor_fn_field_name to use that, but not to
> rely on it.
>
> I need to double-check with the HP reader, but I can probably rely on this
> now, and kill all physname checks for this purpose. One down, N to go, next
> on the hitlist is decode_line_2 once I figure out an approach. Then calling
> functions.
>
> --
> Daniel Jacobowitz
> MontaVista Software Debian GNU/Linux Developer
>
Oops, with patch.
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer
2002-11-01 Daniel Jacobowitz <drow@mvista.com>
* gdbtypes.c (get_destructor_fn_field): Return obvious destructors
based on method name.
Index: gdbtypes.c
===================================================================
RCS file: /cvs/src/src/gdb/gdbtypes.c,v
retrieving revision 1.59.2.1
diff -u -p -r1.59.2.1 gdbtypes.c
--- gdbtypes.c 26 Oct 2002 17:12:07 -0000 1.59.2.1
+++ gdbtypes.c 31 Oct 2002 23:04:35 -0000
@@ -1311,6 +1311,13 @@ get_destructor_fn_field (struct type *t,
int j;
struct fn_field *f = TYPE_FN_FIELDLIST1 (t, i);
+ if (TYPE_FN_FIELDLIST_NAME (t, i)[0] == '~')
+ {
+ *method_indexp = i;
+ *field_indexp = 0;
+ return 1;
+ }
+
for (j = 0; j < TYPE_FN_FIELDLIST_LENGTH (t, i); j++)
{
if (is_destructor_name (TYPE_FN_FIELD_PHYSNAME (f, j)) != 0)
prev parent reply other threads:[~2002-11-01 16:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-01 8:36 Daniel Jacobowitz
2002-11-01 8:43 ` Daniel Jacobowitz [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=20021101164427.GA9014@nevyn.them.org \
--to=drow@mvista.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