[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Qemu-devel] qemu process crash: Assertion failed: QLIST_EMPTY(&bs->
From: |
Stefan Hajnoczi |
Subject: |
Re: [Qemu-devel] qemu process crash: Assertion failed: QLIST_EMPTY(&bs->tracked_requests) |
Date: |
Mon, 29 Jan 2018 16:01:04 +0000 |
User-agent: |
Mutt/1.9.1 (2017-09-22) |
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
signature.asc
Description: PGP signature
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- Re: [Qemu-devel] qemu process crash: Assertion failed: QLIST_EMPTY(&bs->tracked_requests),
Stefan Hajnoczi <=