From: Daniel Berlin <dberlin@redhat.com>
To: Michael Elizabeth Chastain <chastain@cygnus.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFA] testsuite/gdb.c++/ref-types.exp: use runto
Date: Sat, 17 Mar 2001 14:23:00 -0000 [thread overview]
Message-ID: <m2hf0snihn.fsf@dynamic-addr-83-177.resnet.rochester.edu> (raw)
In-Reply-To: <200103172035.MAA10416@bosch.cygnus.com>
Michael Elizabeth Chastain <chastain@cygnus.com> writes:
> Actually, I'm suggesting two things:
>
> (1) In the gdb test suite, print FAIL when gdb gives a wrong answer.
>
> (2) In gdb, figure out a cover set for the cases that fail, and
> don't execute those cases.
>
> "virtual functions altogether" would certainly cover all the buggy cases,
> but it's too broad.
>
> Perhaps "virtual functions in for classes where the complete type has
> a virtual base"?
This is still a lot of cases, because of mixin use.
I think I can come up with a better heuristic.
How bout i do a minimal symbol lookup on the address we think the
virtual function is at, and make sure it's the start of some real
function (and if you really want to go a bit further, i'll make sure
it's a function in the class, or it's base classes)
It's going to be exteremely rare that we come up with an address that
happens to match this heuristic, but isn't correct (because we'll
end up not at the start address of a function 99% of the time if we
are wrong).
--Dan
>
> Michael
next prev parent reply other threads:[~2001-03-17 14:23 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-17 12:35 Michael Elizabeth Chastain
2001-03-17 14:23 ` Daniel Berlin [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-03-17 14:37 Michael Elizabeth Chastain
2001-03-17 12:42 Michael Elizabeth Chastain
2001-03-17 15:31 ` Daniel Berlin
2001-03-16 21:00 Michael Elizabeth Chastain
2001-03-17 11:12 ` Daniel Berlin
2001-03-16 16:03 Michael Elizabeth Chastain
2001-03-16 14:50 Michael Elizabeth Chastain
2001-03-16 14:55 ` Daniel Berlin
2001-03-16 14:49 Michael Elizabeth Chastain
2001-03-16 14:55 ` Daniel Berlin
[not found] ` <20010316215907.A3607@redhat.com>
2001-03-17 11:59 ` Daniel Berlin
2001-03-16 14:35 Michael Elizabeth Chastain
2001-03-16 14:40 ` Fernando Nasser
2001-03-16 14:43 ` Daniel Berlin
2001-03-16 14:44 ` Daniel Berlin
2001-03-16 13:15 Michael Elizabeth Chastain
2001-03-16 13:21 ` Fernando Nasser
2001-03-16 15:14 ` Peter.Schauer
2001-03-16 15:17 ` Daniel Berlin
2001-03-16 15:45 ` Michael Snyder
2001-03-16 15:49 ` Daniel Berlin
2001-03-16 15:19 ` Andrew Cagney
2001-03-16 15:21 ` Daniel Berlin
2001-03-17 7:56 ` Daniel Berlin
[not found] <200103161807.KAA06081@bosch.cygnus.com>
2001-03-16 12:00 ` Fernando Nasser
2001-03-16 13:00 ` Daniel Berlin
2001-03-16 14:29 ` Michael Snyder
2001-03-04 15:25 Michael Elizabeth Chastain
2001-02-24 0:16 Michael Elizabeth Chastain
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=m2hf0snihn.fsf@dynamic-addr-83-177.resnet.rochester.edu \
--to=dberlin@redhat.com \
--cc=chastain@cygnus.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