From: Luiz Capitulino <lcapitulino@redhat.com>
To: "David S. Ahern" <daahern@cisco.com>
Cc: qemu-devel@nongnu.org, kvm-devel <kvm@vger.kernel.org>,
Avi Kivity <avi@redhat.com>
Subject: Re: [Qemu-devel] Qemu terminating with SIGABRT
Date: Mon, 14 Dec 2009 14:04:05 -0200 [thread overview]
Message-ID: <20091214140405.493ecbba@doriath> (raw)
In-Reply-To: <4B23DC62.5090301@cisco.com>
On Sat, 12 Dec 2009 11:09:38 -0700
"David S. Ahern" <daahern@cisco.com> wrote:
> Thanks for the responses. I had forgotten that SIGABRT==abort() which
> means I have to get the core file to get to the root cause. To date the
> only information I have is a shell exit status of 134 which from the
> bash man pages means it died due to SIGABRT.
Are you using qemu-kvm or upstream qemu? Which version? Don't you
have any procedure which would make the bug more likely to happen?
Thanks.
next prev parent reply other threads:[~2009-12-14 16:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-11 17:08 [Qemu-devel] Qemu terminating with SIGABRT David S. Ahern
2009-12-12 8:09 ` [Qemu-devel] " Avi Kivity
2009-12-12 8:52 ` [Qemu-devel] " Stefan Weil
2009-12-12 18:09 ` David S. Ahern
2009-12-14 16:04 ` Luiz Capitulino [this message]
2009-12-14 16:09 ` David S. Ahern
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=20091214140405.493ecbba@doriath \
--to=lcapitulino@redhat.com \
--cc=avi@redhat.com \
--cc=daahern@cisco.com \
--cc=kvm@vger.kernel.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).