From: Stefan Hajnoczi <stefanha@gmail.com>
To: "ing. Mario De Chenno" <mario.dechenno@unina2.it>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] qemu-nbd segmentation fault
Date: Wed, 18 Sep 2013 14:50:35 +0200 [thread overview]
Message-ID: <20130918125035.GF13359@stefanha-thinkpad.redhat.com> (raw)
In-Reply-To: <CAE=mWbvLGVtDFis=RziHnZ9xW1N7aqe6J8x7uCp=DZH3LL6H4Q@mail.gmail.com>
On Tue, Sep 17, 2013 at 02:53:51PM +0200, ing. Mario De Chenno wrote:
> I cannot use qemu-nbd to write files to a qcow2 disk image. It always exit
> after a while with a segmentation fault.
Hi Mario,
Thanks for providing the strace. Is it possible for you to post a
backtrace?
The backtrace shows where exactly the segfault occurs. Try this:
$ gdb --args path/to/qemu-nbd test.img
When the qemu-nbd process crashes you will be at the gdb prompt and can
print the backtrace:
(gdb) bt
Please post the gdb output.
Thanks,
Stefan
next prev parent reply other threads:[~2013-09-18 12:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-17 12:53 [Qemu-devel] qemu-nbd segmentation fault ing. Mario De Chenno
2013-09-18 12:50 ` Stefan Hajnoczi [this message]
2013-09-18 13:35 ` [Qemu-devel] R: " Mario DE CHENNO
2013-09-19 10:05 ` Stefan Hajnoczi
2013-10-02 8:32 ` Stefan Hajnoczi
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=20130918125035.GF13359@stefanha-thinkpad.redhat.com \
--to=stefanha@gmail.com \
--cc=mario.dechenno@unina2.it \
--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).