From: Luis Machado <luis.machado@arm.com>
To: Tom de Vries <tdevries@suse.de>, Tom Tromey <tom@tromey.com>,
Tom de Vries via Gdb-patches <gdb-patches@sourceware.org>
Subject: Re: [pushed] [gdb/testsuite] Clean up before compilation in gdb.ada/call-no-debug.exp
Date: Mon, 19 Jun 2023 15:25:39 +0100 [thread overview]
Message-ID: <9c0db209-2d05-213c-0491-1debe35fb403@arm.com> (raw)
In-Reply-To: <30dc92ca-6fd5-46f1-d716-463be55cba98@suse.de>
On 6/17/23 11:50, Tom de Vries via Gdb-patches wrote:
> On 6/16/23 20:38, Tom Tromey wrote:
>>>>>>> "Tom" == Tom de Vries via Gdb-patches <gdb-patches@sourceware.org> writes:
>>
>> Tom> Running test-case gdb.ada/call-no-debug.exp with target board unix/-m64 works
>> Tom> fine, but if we run it again with target board unix-m32, we run into:
>>
>> Thanks for doing this.
>>
>> If gdb's test suite could detect when a new .exp is started, we could
>> make this always work by removing the corresponding standard output directory.
>
> Hi,
>
> thanks for the suggestion, I've implemented it in gdb_init. WDYT?
>
> Thanks,
> - Tom
Would this delete files unrelated to the specific test being executed? I started to see a number
of errors in the testsuite where tests executed in parallel can't find gdb.log.
For instance:
---
ERROR: tcl error sourcing binutils-gdb/gdb/testsuite/gdb.arch/aarch64-sve.exp.
ERROR: couldn't open "outputs/gdb.arch/aarch64-sve/gdb.log": no such file or directory
while executing
"log_file -a outputs/gdb.arch/aarch64-sve/gdb.log"
("eval" body line 1)
invoked from within
"eval log_file $saved_log"
(procedure "get_compiler_info" line 51)
invoked from within
"get_compiler_info $language"
(procedure "test_compiler_info" line 4)
invoked from within
"test_compiler_info "clang-*""
(procedure "gdb_compile" line 41)
invoked from within
"gdb_compile $src $obj $type $compile_flags"
(procedure "gdb_simple_compile" line 44)
invoked from within
"gdb_simple_compile $name $code $type $compile_flags temp_obj $default_compile_flags"
(procedure "gdb_can_simple_compile" line 2)
invoked from within
"gdb_can_simple_compile aarch32 [join $list \n]"
(procedure "gdb_real__is_aarch32_target" line 15)
invoked from within
"gdb_real__is_aarch32_target"
("uplevel" body line 1)
invoked from within
"uplevel 2 $real_name"
(procedure "gdb_do_cache_wrap" line 3)
invoked from within
"gdb_do_cache_wrap $real_name {*}$args"
(procedure "gdb_do_cache" line 48)
invoked from within
"gdb_do_cache is_aarch32_target"
(procedure "is_aarch32_target" line 1)
invoked from within
"is_aarch32_target"
(procedure "is_aarch64_target" line 6)
invoked from within
"is_aarch64_target"
(procedure "gdb_real__allow_aarch64_sve_tests" line 6)
invoked from within
"gdb_real__allow_aarch64_sve_tests"
("uplevel" body line 1)
invoked from within
"uplevel 2 [list $real_name {*}$args]"
invoked from within
"gdb_do_cache_wrap $real_name {*}$args"
(procedure "gdb_do_cache" line 48)
invoked from within
"gdb_do_cache allow_aarch64_sve_tests"
(procedure "allow_aarch64_sve_tests" line 1)
invoked from within
"allow_aarch64_sve_tests"
("uplevel" body line 1)
invoked from within
"uplevel 1 $fn"
(procedure "require" line 11)
invoked from within
"require allow_aarch64_sve_tests"
(file "binutils-gdb/gdb/testsuite/gdb.arch/aarch64-sve.exp" line 18)
invoked from within
"source binutils-gdb/gdb/testsuite/gdb.arch/aarch64-sve.exp"
("uplevel" body line 1)
invoked from within
"uplevel #0 source binutils-gdb/gdb/testsuite/gdb.arch/aarch64-sve.exp"
invoked from within
"catch "uplevel #0 source $test_file_name""
---
When reverting this patch, I no longer see the problem. Maybe it is deleting more than it should?
next prev parent reply other threads:[~2023-06-19 14:25 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-16 11:33 Tom de Vries
2023-06-16 18:38 ` Tom Tromey
2023-06-17 10:50 ` Tom de Vries
2023-06-17 20:14 ` Tom Tromey
2023-06-19 14:25 ` Luis Machado [this message]
2023-06-19 14:26 ` Luis Machado
2023-06-19 17:12 ` Tom de Vries
2023-06-19 17:22 ` Tom Tromey
2023-06-21 5:31 ` Tom de Vries
2023-06-21 7:40 ` Luis Machado
2023-06-22 16:01 ` Tom Tromey
2023-06-19 17:19 ` 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=9c0db209-2d05-213c-0491-1debe35fb403@arm.com \
--to=luis.machado@arm.com \
--cc=gdb-patches@sourceware.org \
--cc=tdevries@suse.de \
--cc=tom@tromey.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).