From: Peter Maydell <peter.maydell@linaro.org>
To: qemu-devel@nongnu.org
Cc: patches@linaro.org, "Richard Henderson" <rth@twiddle.net>,
"Philippe Mathieu-Daudé" <f4bug@amsat.org>,
"Alex Bennée" <alex.bennee@linaro.org>,
"Michael S . Tsirkin" <mst@redhat.com>
Subject: [Qemu-devel] [PATCH for-3.0] tests/libqtest: Improve kill_qemu() assert
Date: Mon, 23 Jul 2018 19:47:52 +0100 [thread overview]
Message-ID: <20180723184752.22150-1-peter.maydell@linaro.org> (raw)
In kill_qemu() we have an assert that checks that the QEMU process
didn't dump core:
assert(!WCOREDUMP(wstatus));
Unfortunately the WCOREDUMP macro here means the resulting message
is not very easy to comprehend on at least some systems:
ahci-test: tests/libqtest.c:113: kill_qemu: Assertion `!(((__extension__ (((union { __typeof(wstatus) __in; int __i; }) { .__in = (wstatus) }).__i))) & 0x80)' failed.
and it doesn't identify what signal the process took.
Instead of using a raw assert, print the information in an
easier to understand way:
/i386/ahci/sanity: tests/libqtest.c:119: kill_qemu() tried to terminate QEMU process but it dumped core with signal 11 (Segmentation fault)
Aborted (core dumped)
(Of course, the really useful information would be why the QEMU
process dumped core in the first place, but we don't have that
by the time the test program has picked up the exit status.)
Signed-off-by: Peter Maydell <peter.maydell@linaro.org>
---
changes v1->v2: addressed some of the bikeshedding with:
* print file-and-line in the fprintf message, and then
just abort(), rather than assert(0)
* print the signal name via strsignal() as well
tests/libqtest.c | 11 ++++++++++-
1 file changed, 10 insertions(+), 1 deletion(-)
diff --git a/tests/libqtest.c b/tests/libqtest.c
index 098af6aec44..bfc86a15f4b 100644
--- a/tests/libqtest.c
+++ b/tests/libqtest.c
@@ -110,7 +110,16 @@ static void kill_qemu(QTestState *s)
pid = waitpid(s->qemu_pid, &wstatus, 0);
if (pid == s->qemu_pid && WIFSIGNALED(wstatus)) {
- assert(!WCOREDUMP(wstatus));
+ if (WCOREDUMP(wstatus)) {
+ int sig = WTERMSIG(wstatus);
+ const char *signame = strsignal(sig) ?: "unknown ???";
+
+ fprintf(stderr,
+ "%s:%d: kill_qemu() tried to terminate QEMU "
+ "process but it dumped core with signal %d (%s)\n",
+ __FILE__, __LINE__, sig, signame);
+ abort();
+ }
}
}
}
--
2.17.1
next reply other threads:[~2018-07-23 18:47 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-23 18:47 Peter Maydell [this message]
2018-07-23 18:59 ` [Qemu-devel] [PATCH for-3.0] tests/libqtest: Improve kill_qemu() assert Eric Blake
2018-07-23 19:02 ` Peter Maydell
2018-07-23 19:46 ` Eric Blake
-- strict thread matches above, loose matches on Subject: below --
2018-07-20 15:39 [Qemu-devel] [PATCH for-3.0 ?] " Peter Maydell
2018-07-20 15:48 ` Philippe Mathieu-Daudé
2018-07-20 15:49 ` Peter Maydell
2018-07-20 16:14 ` Richard Henderson
2018-07-20 16:25 ` Peter Maydell
2018-07-20 16:36 ` Richard Henderson
2018-07-20 16:45 ` Peter Maydell
2018-07-20 17:28 ` Richard Henderson
2018-07-22 15:27 ` Michael S. Tsirkin
2018-07-23 10:59 ` Alex Bennée
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=20180723184752.22150-1-peter.maydell@linaro.org \
--to=peter.maydell@linaro.org \
--cc=alex.bennee@linaro.org \
--cc=f4bug@amsat.org \
--cc=mst@redhat.com \
--cc=patches@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=rth@twiddle.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;
as well as URLs for NNTP newsgroup(s).