From: Paul Brook <paul@codesourcery.com>
To: qemu-devel@nongnu.org
Cc: riku.voipio@iki.fi
Subject: Re: [Qemu-devel] [PATCH 3/5] linux-user: do not avoid dumping of qemu itself
Date: Tue, 30 Jun 2009 15:52:12 +0100 [thread overview]
Message-ID: <200906301552.12732.paul@codesourcery.com> (raw)
In-Reply-To: <14dcb210bb69620dd6a6912c66827da3aba4784c.1246370192.git.riku.voipio@iki.fi>
On Tuesday 30 June 2009, riku.voipio@iki.fi wrote:
> From: Riku Voipio <riku.voipio@iki.fi>
>
> Previously we disabled dumping of qemu itself if we already
> created coredump of the target process. This broke the abort01
> LTP test and any application that used WCOREDUMP to find out
> the child process dumped core. Remove this feature.
Isn't this going to overwrite the guest core dump we just wrote?
It sounds like WCOREDUMP is one of those things that just isn't going to work.
i.e. we have to just accept the limitation and xfail the test.
Paul
next prev parent reply other threads:[~2009-06-30 14:52 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-30 14:15 [Qemu-devel] [PATCH 0/5] Fixes for linux-user riku.voipio
2009-06-30 14:15 ` [Qemu-devel] [PATCH 1/5] linux-user: increment MAX_ARG_PAGES riku.voipio
2009-06-30 14:15 ` [Qemu-devel] [PATCH 2/5] linux-user: check some parameters for some socket syscalls riku.voipio
2009-06-30 14:15 ` [Qemu-devel] [PATCH 3/5] linux-user: do not avoid dumping of qemu itself riku.voipio
2009-06-30 14:52 ` Paul Brook [this message]
2009-06-30 17:01 ` Riku Voipio
2009-07-01 20:34 ` Arnaud Patard
2009-07-01 23:31 ` Paul Brook
2009-07-02 2:19 ` Jamie Lokier
2009-07-02 13:19 ` Paul Brook
2009-07-02 20:01 ` Riku Voipio
2009-07-03 2:25 ` Jamie Lokier
2009-07-03 2:20 ` Jamie Lokier
2009-06-30 14:15 ` [Qemu-devel] [PATCH 4/5] linux-user/syscall.c: remove warning: ‘array’ may be used uninitialized in this function riku.voipio
2009-06-30 14:15 ` [Qemu-devel] [PATCH 5/5] configure: remove bogus linux-user check riku.voipio
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=200906301552.12732.paul@codesourcery.com \
--to=paul@codesourcery.com \
--cc=qemu-devel@nongnu.org \
--cc=riku.voipio@iki.fi \
/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).