From: Pedro Alves <pedro@palves.net>
To: Bruno Larsen <blarsen@redhat.com>, gdb-patches@sourceware.org
Subject: Re: [PATCH 01/11] change gdb.base/skip.exp to use finish instead of step
Date: Wed, 2 Mar 2022 16:11:01 +0000 [thread overview]
Message-ID: <50f75fc6-df4b-8408-4843-7d3363ed6f1a@palves.net> (raw)
In-Reply-To: <20220126195053.69559-2-blarsen@redhat.com>
On 2022-01-26 19:50, Bruno Larsen via Gdb-patches wrote:
> skip.exp was making use of a fixed amount of step commands to exit
> some functions. This caused some problems when testing GDB with clang,
> as it doesn't add epilogue information for functions. Since the step
> commands weren't testing important features, they were changed to finish
> commands.
I'm not a fan of _completely_ avoiding stepping out of functions, due to some
compilers misbehaving. I mean, if we're going to do this throughout
the testsuite, then we should at least have one testcase that is explicitly
about stepping out of a function with step, one that exhibits the problem,
and we can concentrate the xfails there (and we should press the compiler
folks to fix it). I'm not sure we have one. If we do, you should mention it
explicitly in the commit log. Afterall, users will be doing this too.
next prev parent reply other threads:[~2022-03-02 16:11 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-26 19:50 [PATCH 00/11] gdb/testsuite: Cleanup gdb.base for clang testing Bruno Larsen
2022-01-26 19:50 ` [PATCH 01/11] change gdb.base/skip.exp to use finish instead of step Bruno Larsen
2022-02-25 17:00 ` Andrew Burgess
2022-03-02 16:11 ` Pedro Alves [this message]
2022-03-02 16:39 ` Andrew Burgess
2022-03-07 19:59 ` Bruno Larsen
2022-01-26 19:50 ` [PATCH 02/11] change gdb.base/symbol-alias to xfail with clang Bruno Larsen
2022-01-26 19:50 ` [PATCH 03/11] Change gdb.base/skip-solib.exp deal with lack of epilogue information Bruno Larsen
2022-03-02 16:17 ` Pedro Alves
2022-03-07 19:53 ` Bruno Larsen
2022-01-26 19:50 ` [PATCH 04/11] change gdb.base/nodebug.c to not fail with clang Bruno Larsen
2022-01-26 19:50 ` [PATCH 05/11] update gdb.base/info-program.exp " Bruno Larsen
2022-01-26 19:50 ` [PATCH 06/11] fix gdb.base/access-mem-running.exp for clang testing Bruno Larsen
2022-01-26 19:50 ` [PATCH 07/11] fix gdb.base/call-ar-st to work with clang Bruno Larsen
2022-03-02 18:59 ` Pedro Alves
2022-03-04 14:14 ` Tom Tromey
2022-03-07 20:39 ` Bruno Larsen
2022-01-26 19:50 ` [PATCH 08/11] add xfails to gdb.base/complex-parts.exp when testing " Bruno Larsen
2022-03-02 19:10 ` Pedro Alves
2022-01-26 19:50 ` [PATCH 09/11] gdb/testsuite: don't test gdb.base/msym-bp-shl " Bruno Larsen
2022-03-02 19:33 ` Pedro Alves
2022-03-08 12:58 ` Bruno Larsen
2022-03-30 12:19 ` Bruno Larsen
2022-03-31 18:49 ` Pedro Alves
2022-03-31 19:13 ` Bruno Larsen
2022-01-26 19:50 ` [PATCH 10/11] make use of finish to leave function in gdb.base/skip-inline.exp Bruno Larsen
2022-01-26 19:50 ` [PATCH 11/11] explicitly test for stderr in gdb.base/dprintf.exp Bruno Larsen
2022-03-02 16:50 ` Pedro Alves
2022-03-31 13:44 ` Bruno Larsen
2022-03-31 14:31 ` Pedro Alves
2022-02-09 12:03 ` [PING][PATCH 00/11] gdb/testsuite: Cleanup gdb.base for clang testing Bruno Larsen
2022-02-21 12:53 ` [PINGv2][PATCH " Bruno Larsen
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=50f75fc6-df4b-8408-4843-7d3363ed6f1a@palves.net \
--to=pedro@palves.net \
--cc=blarsen@redhat.com \
--cc=gdb-patches@sourceware.org \
/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).