From: Daniel Jacobowitz <drow@mvista.com>
To: Michael Elizabeth Chastain <mec.gnu@mindspring.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [rfc/cp] method stub assertions
Date: Mon, 05 Jan 2004 19:23:00 -0000 [thread overview]
Message-ID: <20040105192356.GA29254@nevyn.them.org> (raw)
In-Reply-To: <20040105115033.8376A4B35A@berman.michael-chastain.com> <20040105005048.A159C4B35A@berman.michael-chastain.com>
On Sun, Jan 04, 2004 at 07:50:48PM -0500, Michael Chastain wrote:
> I'm working on support for hp-ux aCC.
>
> When I call a C++ method, I get this assertion failure:
>
> call class_param.Aptr_a (&g_A)
> /house/chastain/gdb/s1/gdb/valops.c:1942: internal-error: Assertion `TYPE_DOMAIN_TYPE (fns_ptr[0].type) != NULL' failed.
>
> This assertion is in find_overload_method:
>
> /* If we are dealing with stub method types, they should have
> been resolved by find_method_list via value_find_oload_method_list
> above. */
> gdb_assert (TYPE_DOMAIN_TYPE (fns_ptr[0].type) != NULL);
>
> The "domain type" is a pointer from the method to the base class
> that defines the virtual table for the class that contains this method.
>
> Here is some history about this assertion:
>
> http://sources.redhat.com/ml/gdb-patches/2002-05/msg00413.html
>
> Unfortunately, hpread.c does not set TYPE_DOMAIN_TYPE. As far as I can
> tell, only dwarf2read.c and stabsread.c set this field.
No, that's not correct. hpread.c sets it the same way that
dwarf2read.c does, by calling smash_to_method_type and
smash_to_member_type.
These are only used in hpread for DNTT_TYPE_PTRMEMFUNC and
DNTT_TYPE_PTRMEM.
dwarf2read, however, calls smash_to_method_type when creating a method
type.
> Fortunately, it appears that TYPE_DOMAIN_TYPE is really only needed for
> calls through member pointers or member function pointers. Such calls
> are forbidden with hp-ux som anyways.
>
> This patch adjusts some asserts. I want to change find_overload_method
> so that the code asserts that methods are not stubbed (which is what it
> really needs), and then change evaluate_subexp_standard so that it
> asserts TYPE_DOMAIN_TYPE when it really uses them.
Right now we assume that methods have a TYPE_DOMAIN_TYPE. This patch
pushes more knowledge of limited debug readers out into the rest of
GDB. I'd rather go the other direction - set a domain type. If I'm
reading dwarf2read correctly it simply uses the enclosing class, not
walking back to find the class containing the vtable as you describe
above. It's for _classes_ that it behaves as described above. See the
comment:
/* For types with virtual functions (TYPE_CODE_STRUCT), VPTR_BASETYPE
is the base class which defined the virtual function table pointer.
For types that are pointer to member types (TYPE_CODE_MEMBER),
VPTR_BASETYPE is the type that this pointer is a member of.
For method types (TYPE_CODE_METHOD), VPTR_BASETYPE is the aggregate
type that contains the method.
Unused otherwise. */
> After I do this, gdb gets further, but then crashes anyways in:
>
> evaluate_subexp_standard
> find_overload_match
> value_virtual_fn_field
> gnuv2_virtual_fn_field # WRONG!
> value_primitive_field
> check_typedef
>
> So the next problem after this is that the the abi type is set to
> gnu-v2. When I do "set cp-abi hpaCC", gdb calls the function,
> although I see further problems after that.
You will need to find some way to autodetect this. Does aCC still
produce SOM output, even for hppa64? If so you can use
hp_som_object_present, but that's a gross hack. It would be better to
find another way.
See where we autodetect gnu_v3.
> Anyways, my questions are:
>
> Am I on the right track?
> Can I commit this?
No, please try to set TYPE_DOMAIN_TYPE in hpread instead. I think
around line 3950 is the only place you'll need to. Hmm... or perhaps
calling smash_to_method_type at 3861. That may work.
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2004-01-05 19:23 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-05 11:50 [rfc/cp] take 2: method stubs asserts Michael Elizabeth Chastain
2004-01-05 0:50 ` [rfc/cp] method stub assertions Michael Elizabeth Chastain
2004-01-05 1:56 ` Daniel Jacobowitz
2004-01-05 19:23 ` Daniel Jacobowitz [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-01-06 18:24 Michael Elizabeth Chastain
2004-01-06 19:02 ` Daniel Jacobowitz
2004-01-06 4:28 Michael Elizabeth Chastain
2004-01-06 4:43 ` Daniel Jacobowitz
2004-01-06 17:05 ` Daniel Jacobowitz
2004-01-06 18:41 ` David Carlton
2004-01-06 19:05 ` Daniel Jacobowitz
2004-01-06 0:12 Michael Elizabeth Chastain
2004-01-06 2:51 ` Daniel Jacobowitz
2004-01-05 20:51 Michael Elizabeth Chastain
2004-01-05 2:32 Michael Elizabeth Chastain
2004-01-05 2:33 ` Daniel Jacobowitz
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=20040105192356.GA29254@nevyn.them.org \
--to=drow@mvista.com \
--cc=gdb-patches@sources.redhat.com \
--cc=mec.gnu@mindspring.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