From: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
To: kwolf@redhat.com, mreitz@redhat.com, qemu-devel@nongnu.org,
qemu-block@nongnu.org
Subject: [Qemu-devel] qemu-img seg, test 082 not showing the error
Date: Fri, 14 Aug 2015 13:01:05 +0100 [thread overview]
Message-ID: <20150814120105.GA2250@work-vm> (raw)
Hi,
I noticed that although 'make check-block' was passing happily I was
seeing a kernel log showing a qemu-img seg:
[Fri Aug 14 12:26:07 2015] qemu-img[7725]: segfault at 0 ip (null) sp 00007ffff73e9a98 error 14 in qemu-img[55f707577000+f8000]
The case that fails is:
run_qemu_img amend -f qcow2 -o backing_file=/home/dgilbert/try-world3/tests/qemu-iotests/scratch/t.qcow2, -o help /home/dgilbert/try-world3/tests/qemu-iotests/scratch/t.qcow2
and I think the problem is due to a disagreement between
626f84f3 - qemu-img amend: Support multiple -o options
and
76a3a34d - qemu-img: Add progress output for amend
In the 'Invalid option list' case it goto's out skipping
the qemu_progress_init, but the out: clause does a
qemu_progress_end that then segs.
However, I've not dug into why the testcase code didn't
spot it, which seems a more important problem.
Dave
--
Dr. David Alan Gilbert / dgilbert@redhat.com / Manchester, UK
reply other threads:[~2015-08-14 12:01 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20150814120105.GA2250@work-vm \
--to=dgilbert@redhat.com \
--cc=kwolf@redhat.com \
--cc=mreitz@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.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 NNTP newsgroup(s).