From: Simon Marchi <simark@simark.ca>
To: Weimin Pan <weimin.pan@oracle.com>, gdb-patches@sourceware.org
Subject: Re: [PATCH PR gdb/16841] virtual inheritance via typedef cannot find base
Date: Sun, 17 Jun 2018 01:06:00 -0000 [thread overview]
Message-ID: <97eae4ee-dc9b-2c02-83e2-d35974319ed2@simark.ca> (raw)
In-Reply-To: <1529106313-11806-1-git-send-email-weimin.pan@oracle.com>
On 2018-06-15 07:45 PM, Weimin Pan wrote:
> Fix failure to find member of a typedef base class
>
> The test case below demonstrates the problem, as described in this PR's Comment 5:
>
> typedef struct {
> int x;
> } A;
>
> struct C : A {
> int y;
> };
>
> int main()
> {
> C c;
> return 55;
> }
>
> $ gdb a.out
> (gdb) ptype C::x
> Internal error: non-aggregate type to value_struct_elt_for_reference
>
> In value_struct_elt_for_reference(), need to call check_typedef() on
> the aggregate type to handle the case of *curtype being ptr->typedef.
Thanks, that makes sense. I noted some nits, you can push the patch after
addressing them.
> diff --git a/gdb/testsuite/ChangeLog b/gdb/testsuite/ChangeLog
> index b2938b1..78771d3 100644
> --- a/gdb/testsuite/ChangeLog
> +++ b/gdb/testsuite/ChangeLog
> @@ -1,3 +1,9 @@
> +2018-06-12 Weimin Pan <weimin.pan@oracle.com>
> +
> + PR gdb/16841
> + * gdb/testsuite/gdb.cp/typedef-base-ptype.cc: New file.
> + * gdb/testsuite/gdb.cp/typedef-base-ptype.exp: New file.
Filenames should be relative to the ChangeLog file, so remove "gdb/testsuite/".
> diff --git a/gdb/testsuite/gdb.cp/typedef-base-ptype.cc b/gdb/testsuite/gdb.cp/typedef-base-ptype.cc
> new file mode 100644
> index 0000000..bfbcc4a
> --- /dev/null
> +++ b/gdb/testsuite/gdb.cp/typedef-base-ptype.cc
> @@ -0,0 +1,30 @@
> +/* This testcase is part of GDB, the GNU debugger.
> +
> + Copyright 2018 Free Software Foundation, Inc.
> +
> + This program is free software; you can redistribute it and/or modify
> + it under the terms of the GNU General Public License as published by
> + the Free Software Foundation; either version 3 of the License, or
> + (at your option) any later version.
> +
> + This program is distributed in the hope that it will be useful,
> + but WITHOUT ANY WARRANTY; without even the implied warranty of
> + MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
> + GNU General Public License for more details.
> +
> + You should have received a copy of the GNU General Public License
> + along with this program. If not, see <http://www.gnu.org/licenses/>. */
> +
> +typedef struct {
> + int x;
> +} A;
> +
> +struct C : A {
> + int y;
> +};
> +
> +int main()
> +{
> + C c;
> + return 55;
> +}
We try to make the test code follow the GNU coding style (unless testing
a particular formatting is the purpose of the test).
> diff --git a/gdb/testsuite/gdb.cp/typedef-base-ptype.exp b/gdb/testsuite/gdb.cp/typedef-base-ptype.exp
I would suggest naming this test "typedef-base.exp", because we may add other tests
than ptype in it. For example, David's original reproducer in PR 16841 still won't
work after this patch (AFAIK), and would be a good candidate to end up as a test in
this file.
> new file mode 100644
> index 0000000..e588fd3
> --- /dev/null
> +++ b/gdb/testsuite/gdb.cp/typedef-base-ptype.exp
> @@ -0,0 +1,37 @@
> +# Copyright 2018 Free Software Foundation, Inc.
> +
> +# This program is free software; you can redistribute it and/or modify
> +# it under the terms of the GNU General Public License as published by
> +# the Free Software Foundation; either version 3 of the License, or
> +# (at your option) any later version.
> +#
> +# This program is distributed in the hope that it will be useful,
> +# but WITHOUT ANY WARRANTY; without even the implied warranty of
> +# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
> +# GNU General Public License for more details.
> +#
> +# You should have received a copy of the GNU General Public License
> +# along with this program. If not, see <http://www.gnu.org/licenses/>.
Can you add a one-liner comment that states the purpose of the test? Something
like
# Make sure that inheritance through a typedef is well handled.
Thanks,
Simon
next prev parent reply other threads:[~2018-06-17 1:06 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-15 23:45 Weimin Pan
2018-06-17 1:06 ` Simon Marchi [this message]
2018-06-18 16:12 ` Wei-min Pan
2018-07-20 23:50 Weimin Pan
2018-07-24 22:18 ` Simon Marchi
2018-07-24 23:26 ` Weimin Pan
2018-07-29 2:28 ` Tom Tromey
2018-07-30 17:58 ` Wei-min Pan
2018-07-31 15:42 ` Tom Tromey
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=97eae4ee-dc9b-2c02-83e2-d35974319ed2@simark.ca \
--to=simark@simark.ca \
--cc=gdb-patches@sourceware.org \
--cc=weimin.pan@oracle.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