From: Peter Maydell <peter.maydell@linaro.org>
To: qemu-devel@nongnu.org
Cc: patches@linaro.org, Riku Voipio <riku.voipio@iki.fi>,
Laurent Vivier <laurent@vivier.eu>,
Chris Wulff <crwulff@gmail.com>, Marek Vasut <marex@denx.de>
Subject: [Qemu-devel] [PATCH 0/2] linux-user: Don't call gdb_handlesig unnecessarily
Date: Fri, 19 Oct 2018 18:49:56 +0100 [thread overview]
Message-ID: <20181019174958.26616-1-peter.maydell@linaro.org> (raw)
This patchset fixes a minor bug in our handling of SIGTRAP
in linux-user.
The CPU main-loop routines for linux-user generally call
gdb_handlesig() when they're about to queue a SIGTRAP signal. This
is wrong, because queue_signal() will cause us to pend a signal, and
process_pending_signals() will then call gdb_handlesig() itself. So
the effect is that we notify gdb of the SIGTRAP, and then if gdb says
"OK, continue with signal X" we will incorrectly notify gdb of the
signal X as well. We don't do this double-notify for anything else,
only SIGTRAP.
This bug only manifests if the user responds to the reported SIGTRAP
using "signal SIGFOO" rather than "continue"; since the latter is the
overwhelmingly common thing to do after a breakpoint most people
won't have hit this.
Patch 1 fixes this bug for every target except nios2, by
deleting the incorrect code.
Patch 2 fixes nios2 separately, because it was doing some odd
things with gdb_handlesig(). This also fixes in passing a Coverity
issue.
Tested with "make check-tcg", and with some by-hand stepping
around with an attached gdb. NB that the nios2 patch is only
compile tested as I don't have a nios2 linux-user environment
and check-tcg doesn't cover it.
thanks
-- PMM
Peter Maydell (2):
linux-user: Don't call gdb_handlesig() before queue_signal()
linux-user: Clean up nios2 main loop signal handling
linux-user/aarch64/cpu_loop.c | 13 +++++--------
linux-user/alpha/cpu_loop.c | 12 ++++--------
linux-user/arm/cpu_loop.c | 16 ++++------------
linux-user/cris/cpu_loop.c | 16 ++++------------
linux-user/hppa/cpu_loop.c | 11 ++++-------
linux-user/i386/cpu_loop.c | 16 ++++------------
linux-user/m68k/cpu_loop.c | 16 ++++------------
linux-user/microblaze/cpu_loop.c | 16 ++++------------
linux-user/mips/cpu_loop.c | 16 ++++------------
linux-user/nios2/cpu_loop.c | 14 +++++---------
linux-user/openrisc/cpu_loop.c | 11 ++++-------
linux-user/ppc/cpu_loop.c | 15 +++++----------
linux-user/riscv/cpu_loop.c | 2 +-
linux-user/s390x/cpu_loop.c | 9 +++------
linux-user/sh4/cpu_loop.c | 17 ++++-------------
linux-user/sparc/cpu_loop.c | 16 ++++------------
linux-user/xtensa/cpu_loop.c | 11 ++++-------
17 files changed, 67 insertions(+), 160 deletions(-)
--
2.19.1
next reply other threads:[~2018-10-19 17:58 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-19 17:49 Peter Maydell [this message]
2018-10-19 17:49 ` [Qemu-devel] [PATCH 1/2] linux-user: Don't call gdb_handlesig() before queue_signal() Peter Maydell
2018-10-19 17:49 ` [Qemu-devel] [PATCH 2/2] linux-user: Clean up nios2 main loop signal handling Peter Maydell
2018-11-12 16:12 ` Laurent Vivier
2018-10-20 19:49 ` [Qemu-devel] [PATCH 0/2] linux-user: Don't call gdb_handlesig unnecessarily Richard Henderson
2018-11-12 14:39 ` Peter Maydell
2018-11-12 14:46 ` Laurent Vivier
2018-11-12 14:48 ` Peter Maydell
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=20181019174958.26616-1-peter.maydell@linaro.org \
--to=peter.maydell@linaro.org \
--cc=crwulff@gmail.com \
--cc=laurent@vivier.eu \
--cc=marex@denx.de \
--cc=patches@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=riku.voipio@iki.fi \
/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 NNTP newsgroup(s).