From: Tom de Vries <tdevries@suse.de>
To: Carl Love <cel@us.ibm.com>, gdb-patches@sourceware.org
Cc: Ulrich Weigand <Ulrich.Weigand@de.ibm.com>,
Tom Tromey <tom@tromey.com>,
Will Schmidt <will_schmidt@vnet.ibm.com>
Subject: Re: [pushed] [gdb/testsuite] Fix gdb.ada/out_of_line_in_inlined.exp for ppc64le
Date: Mon, 28 Nov 2022 22:31:00 +0100 [thread overview]
Message-ID: <3d15ada9-ea26-e77a-26ed-5860bb83c113@suse.de> (raw)
In-Reply-To: <bc0abf936cfec288e62ccc5df3c767bc0d88fc2d.camel@us.ibm.com>
On 11/28/22 22:07, Carl Love wrote:
> Tom:
>
> On Mon, 2022-11-28 at 21:46 +0100, Tom de Vries wrote:
>>> I made the change $decimal\\.$decimal? and that seemed
>>> to work on my system. I tried the test on my X86 box but it is not
>>> supported. Looks like the system doesn't have the ada compiler
>>> installed.
>>>
>>> Can you verify that the change works on your system and if the
>>> patch
>>> looks ok. Thanks.
>>>
>>
>> It doesn't work, as expected, because the output is:
>> ...
>> Breakpoint 1, foo_o224_021.child1.child2 (s=...) at
>> /home/vries/gdb_versions/devel/binutils-
>> gdb.git/gdb/testsuite/gdb.ada/out_of_line_in_inlined/foo_o224_021.adb
>> :24^M
>> ...
>> and $decimal\\.$decimal? does not match "1".
>
> If I use the original suggestion, here is the patch I ran:
>
> diff --git a/gdb/testsuite/gdb.ada/out_of_line_in_inlined.exp b/gdb/testsuite/gdb.ada/out_of_line_in_inlined.exp
> index 621b04e179b..54c55bc6f7e 100644
> --- a/gdb/testsuite/gdb.ada/out_of_line_in_inlined.exp
> +++ b/gdb/testsuite/gdb.ada/out_of_line_in_inlined.exp
> @@ -34,7 +34,7 @@ foreach_with_prefix scenario {all minimal} {
>
> gdb_run_cmd
> gdb_test "" \
> - "Breakpoint $decimal, ($hex in )?foo_o224_021\\.child1\\.child2 \\(s=\\.\\.\\.\\).*" \
> + "Breakpoint $decimal(\\.$decimal)?, ($hex in )?foo_o224_021\\.child1\\.child2 \\(s=\\.\\.\\.\\).*" \
> "run to foo_o224_021.child1.child2"
>
> set opt_addr_in "($hex in)?"
>
> then I run the test I get:
>
> make check RUNTESTFLAGS='GDB=/home/carll/bin/gdb gdb.ada/out_of_line_in_inlined.exp ' > out
> WARNING: Couldn't find the global config file.
> WARNING: Couldn't find tool init file
> WARNING: Couldn't find the global config file.
> WARNING: Couldn't find tool init file
> WARNING: Couldn't find the global config file.
> WARNING: Couldn't find tool init file
> WARNING: Couldn't find the global config file.
> WARNING: No tool specified
> WARNING: Couldn't find the global config file.
> ERROR: tcl error sourcing /home/carll/GDB/build-test/gdb/testsuite/../../../binutils-gdb-test/gdb/testsuite/gdb.ada/out_of_line_in_inlined.exp.
> ERROR: tcl error code TCL LOOKUP VARNAME decimal
> ERROR: can't read "decimal(\.[0-9]+)": variable isn't array
Ah I see, yes the $var($index) is tcl syntax for accessing an array element.
So, this should work: ${decimal}(\\.$decimal)?
Thanks,
- Tom
next prev parent reply other threads:[~2022-11-28 21:31 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-28 16:21 Tom de Vries
2022-11-28 17:45 ` Carl Love
2022-11-28 18:08 ` Tom de Vries
2022-11-28 19:55 ` Carl Love
2022-11-28 20:46 ` Tom de Vries
2022-11-28 21:07 ` Carl Love
2022-11-28 21:31 ` Tom de Vries [this message]
2022-11-28 21:44 ` Carl Love
2022-11-28 22:09 ` Tom de Vries
2022-11-28 23:01 ` Carl Love
2022-11-29 7:24 ` Tom de Vries
2022-11-28 21:33 ` Carl Love
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=3d15ada9-ea26-e77a-26ed-5860bb83c113@suse.de \
--to=tdevries@suse.de \
--cc=Ulrich.Weigand@de.ibm.com \
--cc=cel@us.ibm.com \
--cc=gdb-patches@sourceware.org \
--cc=tom@tromey.com \
--cc=will_schmidt@vnet.ibm.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).