From: Stefan Hajnoczi <stefanha@gmail.com>
To: "Fernando Casas Schössow" <casasfernando@hotmail.com>
Cc: qemu-devel <qemu-devel@nongnu.org>,
"qemu-block@nongnu.org" <qemu-block@nongnu.org>,
Jeff Cody <jcody@redhat.com>
Subject: Re: [Qemu-devel] qemu process crash: Assertion failed: QLIST_EMPTY(&bs->tracked_requests)
Date: Mon, 29 Jan 2018 16:01:04 +0000 [thread overview]
Message-ID: <20180129160104.GN20446@stefanha-x1.localdomain> (raw)
In-Reply-To: <VI1PR10MB0301BD1873225A06B658C988B7350@VI1PR10MB0301.EURPRD10.PROD.OUTLOOK.COM>
[-- Attachment #1: Type: text/plain, Size: 697 bytes --]
On Wed, Dec 13, 2017 at 03:33:01PM +0000, Fernando Casas Schössow wrote:
> Maybe I’m missing something here but, if I recall correctly, the qemu process for the guest is terminated when this problem happens. So how a debugger will be attached to a process that is gone?
Sorry, this got lost in my inbox.
assert(false) sends SIGABRT to the process. The default behavior is to
dump a core file that can be analyzed later with GDB.
Your system must have core dumps enabled (i.e. ulimit -c unlimited).
Also, various pieces of software like systemd's coredumpctl can
influence where and how core dumps are stored.
But in short, an assertion failure produces a core dump.
Stefan
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 455 bytes --]
next prev parent reply other threads:[~2018-01-29 16:01 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-07 10:18 [Qemu-devel] qemu process crash: Assertion failed: QLIST_EMPTY(&bs->tracked_requests) Fernando Casas Schössow
2017-12-11 11:56 ` Stefan Hajnoczi
2017-12-11 13:42 ` Fernando Casas Schössow
2017-12-13 11:23 ` Stefan Hajnoczi
2017-12-13 15:33 ` Fernando Casas Schössow
2018-01-29 16:01 ` Stefan Hajnoczi [this message]
2018-10-18 12:25 ` Fernando Casas Schössow
2018-10-18 12:38 ` [Qemu-devel] [Qemu-block] " Kevin Wolf
2018-10-18 13:40 ` Fernando Casas Schössow
[not found] ` <AM6PR10MB2247D63F532AE33155BA57EFB7F80@AM6PR10MB2247.EURPRD10.PROD.OUTLOOK.C OM>
2018-11-16 11:04 ` Fernando Casas Schössow
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=20180129160104.GN20446@stefanha-x1.localdomain \
--to=stefanha@gmail.com \
--cc=casasfernando@hotmail.com \
--cc=jcody@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).