From: Simon Marchi via Gdb-patches <gdb-patches@sourceware.org>
To: Lancelot SIX <lsix@lancelotsix.com>,
Simon Marchi <simon.marchi@efficios.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] gdb: call check_typedef at beginning of dwarf_expr_context::fetch_result
Date: Thu, 28 Jul 2022 11:33:01 -0400 [thread overview]
Message-ID: <c5ea6536-36a3-3950-0c4b-68cbb4aea8ec@simark.ca> (raw)
In-Reply-To: <20220728085607.hicavv2k2tg4jfew@octopus>
On 7/28/22 04:56, Lancelot SIX via Gdb-patches wrote:
> Hi,
>
> [...]
>> diff --git a/gdb/testsuite/gdb.dwarf2/entry-value-typedef.exp b/gdb/testsuite/gdb.dwarf2/entry-value-typedef.exp
>> new file mode 100644
>> index 00000000000..3a3740234fa
>> --- /dev/null
>> +++ b/gdb/testsuite/gdb.dwarf2/entry-value-typedef.exp
>> @@ -0,0 +1,36 @@
>> +# Copyright 2022 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/>.
>> +
>> +# The program associated to this test case uncovered a bug in GDB (PR 29374)
>> +# where a typedef type was used before it was resolved.
>> +
>> +standard_testfile .S
>
> Shouldn’t there be something like:
>
> if { ![istarget x86_64-*-linux* ] } {
> return
> }
>
> or similar to make sure that we do not try to compile this .S file on
> incompatible archs?
Good idea. I assumed the gdb_compile would fail and make us skip the
test on incompatible architectures, but it spews a lot of errors, so
it's cleaner to filter ahead on the arch. I tested this on an aarch64
machine, and then thought I could add a version of the .S for aarch64,
on which I could reproduce the bug too, so the v3 includes that.
Simon
next prev parent reply other threads:[~2022-07-28 15:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-28 1:34 Simon Marchi via Gdb-patches
2022-07-28 2:33 ` [PATCH v2] " Simon Marchi via Gdb-patches
2022-07-28 8:56 ` [PATCH] " Lancelot SIX via Gdb-patches
2022-07-28 15:33 ` Simon Marchi via Gdb-patches [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-07-24 3:59 Simon Marchi via Gdb-patches
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=c5ea6536-36a3-3950-0c4b-68cbb4aea8ec@simark.ca \
--to=gdb-patches@sourceware.org \
--cc=lsix@lancelotsix.com \
--cc=simark@simark.ca \
--cc=simon.marchi@efficios.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