From: Tom Tromey <tom@tromey.com>
To: Tom de Vries <tdevries@suse.de>
Cc: Tom Tromey <tom@tromey.com>, gdb-patches@sourceware.org
Subject: Re: [PATCH 2/3] [gdb/testsuite] Kill left-over process in gdb.base/add-symbol-file-attach.exp
Date: Mon, 24 Feb 2025 11:05:02 -0700 [thread overview]
Message-ID: <87eczn5icx.fsf@tromey.com> (raw)
In-Reply-To: <91ab3691-d4a7-4909-9b2c-6d563bb1dad8@suse.de> (Tom de Vries's message of "Mon, 24 Feb 2025 18:57:35 +0100")
>>>>> "Tom" == Tom de Vries <tdevries@suse.de> writes:
>> Should this really yield unsupported, though, and not a fail?
Tom> AFAIU, the only thing that FAIL should be used for, is if gdb is
Tom> behaving incorrectly. In this case, gdb is not involved, this is just
Tom> expact spawning a process for gdb to attach to.
Yeah, that makes sense. But I think it also makes sense to
differentiate between "cannot run because you don't have a C++ compiler"
and "spawn failed somehow but should not have".
The former is an expected thing -- you didn't want to test C++ or Ada or
whatever.
The latter is some kind of error.
Tom
next prev parent reply other threads:[~2025-02-24 18:06 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-17 16:36 [PATCH 0/3] [gdb/testsuite] Clean up left-over processes Tom de Vries
2025-02-17 16:36 ` [PATCH 1/3] [gdb/testsuite] Don't start gdb in gdb.base/gstack.exp Tom de Vries
2025-02-17 17:20 ` Keith Seitz
2025-02-18 7:59 ` Tom de Vries
2025-02-17 16:36 ` [PATCH 2/3] [gdb/testsuite] Kill left-over process in gdb.base/add-symbol-file-attach.exp Tom de Vries
2025-02-24 17:26 ` Tom Tromey
2025-02-24 17:57 ` Tom de Vries
2025-02-24 18:05 ` Tom Tromey [this message]
2025-02-24 18:43 ` Tom de Vries
2025-02-17 16:36 ` [PATCH 3/3] [gdb/testsuite] Exit left-over gdb in gdb.mi/mi-break.exp Tom de Vries
2025-02-24 17:28 ` 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=87eczn5icx.fsf@tromey.com \
--to=tom@tromey.com \
--cc=gdb-patches@sourceware.org \
--cc=tdevries@suse.de \
/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