From: Stefan Weil <weil@mail.berlios.de>
To: "David S. Ahern" <daahern@cisco.com>
Cc: qemu-devel@nongnu.org, kvm-devel <kvm@vger.kernel.org>
Subject: Re: [Qemu-devel] Qemu terminating with SIGABRT
Date: Sat, 12 Dec 2009 09:52:11 +0100 [thread overview]
Message-ID: <4B2359BB.9070703@mail.berlios.de> (raw)
In-Reply-To: <4B227C7E.3090807@cisco.com>
David S. Ahern schrieb:
> I realize this is a rather generic question, but what are typical
> reasons Qemu would be killed by a SIGABRT? I am seeing this on a
> somewhat regular (though not repeatable on demand) basis. I do not have
> a core file, though I hope to capture one if I can get it repeat again.
>
> Thanks,
>
Look for "abort" in QEMU's code to see the possible reasons.
In many cases, the reason will be printed to stderr before
aborting. Did you call QEMU from a console and get some
output there? Or maybe the stderr output went into a file?
Run "ulimit -c unlimited" before you run QEMU, then a
core file will be written automatically on SIGABRT.
next prev parent reply other threads:[~2009-12-12 8:52 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-11 17:08 Qemu terminating with SIGABRT David S. Ahern
2009-12-11 17:08 ` [Qemu-devel] " David S. Ahern
2009-12-11 18:11 ` Juan Quintela
2009-12-12 8:09 ` Avi Kivity
2009-12-12 8:09 ` [Qemu-devel] " Avi Kivity
2009-12-12 8:52 ` Stefan Weil [this message]
2009-12-12 18:09 ` David S. Ahern
2009-12-12 18:09 ` [Qemu-devel] " David S. Ahern
2009-12-14 16:04 ` Luiz Capitulino
2009-12-14 16:04 ` Luiz Capitulino
2009-12-14 16:09 ` David S. Ahern
2009-12-14 16:09 ` David S. Ahern
2009-12-21 14:16 ` David S. Ahern
2009-12-21 14:22 ` Avi Kivity
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=4B2359BB.9070703@mail.berlios.de \
--to=weil@mail.berlios.de \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.