From: Thiago Jung Bauermann <thiago.bauermann@linaro.org>
To: Pedro Alves <pedro@palves.net>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH v2 03/11] Adjust gdb.base/exitsignal.exp for MinGW, separate program names
Date: Wed, 27 May 2026 18:59:41 -0300 [thread overview]
Message-ID: <87zf1k1pki.fsf@linaro.org> (raw)
In-Reply-To: <20260525191829.984105-4-pedro@palves.net> (Pedro Alves's message of "Mon, 25 May 2026 20:18:21 +0100")
I have just one nit, with two instances in this patch and another
instance in another patch.
Pedro Alves <pedro@palves.net> writes:
> diff --git a/gdb/testsuite/gdb.base/exitsignal.exp b/gdb/testsuite/gdb.base/exitsignal.exp
> index 341197cf0c8..4f4c53e37cb 100644
> --- a/gdb/testsuite/gdb.base/exitsignal.exp
> +++ b/gdb/testsuite/gdb.base/exitsignal.exp
> @@ -23,103 +23,126 @@
>
> require {!target_info exists gdb,nosignals}
>
> -standard_testfile segv.c
> +set testfile "exitsignal"
>
> -if { [prepare_for_testing "failed to prepare" ${testfile} ${srcfile}] } {
> - return
> -}
> +set exec1 "segv"
> +set srcfile1 ${exec1}.c
> +set binfile1 [standard_output_file ${exec1}]
>
> -# Run to main. But, before, change cwd to get the core into the
> -# output directory.
> -set_inferior_cwd_to_output_dir
> +set exec2 "normal"
> +set srcfile2 ${exec2}.c
> +set binfile2 [standard_output_file ${exec2}]
>
> -if { ![runto_main] } {
> - return
> +if { [build_executable "failed to build $exec1" ${exec1} "${srcfile1}" \
> + {debug}] == -1 } {
> + return -1
The current style for testcases is to not return any value from
top-level.
> }
>
> -# Get the inferior's PID for later.
> -set pid [get_inferior_pid]
> -
> -# Print $_exitsignal. It should be void now, because nothing
> -# happened.
> -gdb_test "print \$_exitsignal" " = void" \
> - "\$_exitsignal is void before running"
> -
> -# Just to guarantee, making sure that $_exitcode is also void.
> -gdb_test "print \$_exitcode" " = void" \
> - "\$_exitcode is void before running"
> -
> -# Trigger SIGSEGV.
> -gdb_test "continue" "(Thread .*|Program) received signal SIGSEGV.*" \
> - "trigger SIGSEGV"
> -
> -if {[istarget "*-*-mingw*"]} {
> - # We're debugging a pure Win32 program with no SEH handler. The
> - # previous continue caught the first-chance exception. Now we
> - # catch the second-chance.
> - gdb_test "continue" "Thread .* received signal SIGSEGV.*" \
> - "trigger SIGSEGV, second-chance"
> -} elseif {[istarget "*-*-cygwin*"]} {
> - # Cygwin calls DebugBreak before it lets the process exit.
> - gdb_test "continue" "Thread .* received signal SIGTRAP.*" \
> - "trigger try_to_debug SIGTRAP"
> +if { [build_executable "failed to build $exec2" ${exec2} "${srcfile2}" \
> + {debug}] == -1} {
> + return -1
The current style for testcases is to not return any value from
top-level.
--
Thiago
(he/him)
next prev parent reply other threads:[~2026-05-27 22:00 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-25 19:18 [PATCH v2 00/11] Fix a few Cygwin/MinGW problems Pedro Alves
2026-05-25 19:18 ` [PATCH v2 01/11] Adjust gdb.base/exitsignal.exp for MinGW, trigger fault Pedro Alves
2026-05-25 19:18 ` [PATCH v2 02/11] Adjust gdb.base/exitsignal.exp for MinGW, second-chance SIGSEGV Pedro Alves
2026-05-26 11:18 ` Eli Zaretskii
2026-05-27 12:56 ` Pedro Alves
2026-05-25 19:18 ` [PATCH v2 03/11] Adjust gdb.base/exitsignal.exp for MinGW, separate program names Pedro Alves
2026-05-27 21:59 ` Thiago Jung Bauermann [this message]
2026-06-12 14:00 ` Pedro Alves
2026-05-25 19:18 ` [PATCH v2 04/11] gdb.base/exitsignal.exp: Exit with non-zero Pedro Alves
2026-05-25 19:18 ` [PATCH v2 05/11] gdb.base/exitsignal.exp: Test attaching too Pedro Alves
2026-05-25 19:18 ` [PATCH v2 06/11] gdb/testsuite: Add mechanism to compile Windows native programs on Cygwin Pedro Alves
2026-05-25 19:18 ` [PATCH v2 07/11] Windows gdb+gdbserver: Share exit status logic Pedro Alves
2026-05-25 19:18 ` [PATCH v2 08/11] Windows gdb+gdbserver: Decode Cygwin ExitProcess codes Pedro Alves
2026-05-26 11:31 ` Eli Zaretskii
2026-05-27 13:58 ` Pedro Alves
2026-05-27 14:12 ` Eli Zaretskii
2026-05-27 22:00 ` Thiago Jung Bauermann
2026-05-25 19:18 ` [PATCH v2 09/11] Adjust gdb.python/py-events.exp for Cygwin/MinGW, thread IDs Pedro Alves
2026-05-25 19:18 ` [PATCH v2 10/11] Adjust gdb.python/py-events.exp for Cygwin/MinGW, no fork Pedro Alves
2026-05-25 19:18 ` [PATCH v2 11/11] Adjust gdb.python/py-events.exp for Cygwin/MinGW, "info proc" => "inferior" Pedro Alves
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=87zf1k1pki.fsf@linaro.org \
--to=thiago.bauermann@linaro.org \
--cc=gdb-patches@sourceware.org \
--cc=pedro@palves.net \
/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