qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Eduardo Habkost <ehabkost@redhat.com>
To: qemu-devel@nongnu.org
Cc: Zhang Chen <zhangchen.fnst@cn.fujitsu.com>,
	Li Zhijian <lizhijian@cn.fujitsu.com>
Subject: [Qemu-devel] [PATCH 0/3] device-crash-test: New mode for testing -object
Date: Tue, 13 Jun 2017 20:06:24 -0300	[thread overview]
Message-ID: <20170613230627.17942-1-ehabkost@redhat.com> (raw)

This series extends the device-crash-test script so it can test
backend objects, too.  The new mode can be enabled using the "-O"
option.

The script already found a crash using the following command-line:

  $ qemu-system-x86_64 -S -machine none -object colo-compare,id=test-object
  (qemu-system-x86_64:3812): GLib-CRITICAL **: g_main_loop_quit: assertion 'loop != NULL' failed
  Segmentation fault (core dumped)

Eduardo Habkost (3):
  scripts/qmp: Accept timeout parameter on accept()
  scripts/qemu: Catch QEMU exit while waiting for QMP client
  device-crash-test: Mode for testing -object

 scripts/qemu.py           |  14 ++++++-
 scripts/qmp/qmp.py        |   4 +-
 scripts/device-crash-test | 101 +++++++++++++++++++++++++++++++++-------------
 3 files changed, 89 insertions(+), 30 deletions(-)

-- 
2.11.0.259.g40922b1

             reply	other threads:[~2017-06-13 23:06 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-13 23:06 Eduardo Habkost [this message]
2017-06-13 23:06 ` [Qemu-devel] [PATCH 1/3] scripts/qmp: Accept timeout parameter on accept() Eduardo Habkost
2017-06-13 23:06 ` [Qemu-devel] [PATCH 2/3] scripts/qemu: Catch QEMU exit while waiting for QMP client Eduardo Habkost
2017-06-13 23:06 ` [Qemu-devel] [PATCH 3/3] device-crash-test: Mode for testing -object Eduardo Habkost
2017-06-13 23:20 ` [Qemu-devel] [PATCH 0/3] device-crash-test: New mode " no-reply

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=20170613230627.17942-1-ehabkost@redhat.com \
    --to=ehabkost@redhat.com \
    --cc=lizhijian@cn.fujitsu.com \
    --cc=qemu-devel@nongnu.org \
    --cc=zhangchen.fnst@cn.fujitsu.com \
    /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).