From: Paul Brook <paul@codesourcery.com>
To: qemu-devel@nongnu.org
Cc: riku.voipio@iki.fi
Subject: Re: [Qemu-devel] [PATCH 0/2] linux-user: create coredumps from segfauling target binaries
Date: Thu, 9 Apr 2009 16:27:11 +0100 [thread overview]
Message-ID: <200904091627.11381.paul@codesourcery.com> (raw)
In-Reply-To: <cover.1239287870.git.riku.voipio@iki.fi>
On Thursday 09 April 2009, riku.voipio@iki.fi wrote:
> From: Riku Voipio <riku.voipio@iki.fi>
>
> Instead of exiting with "qemu: uncaught target signal 11", give a coredump.
This needs to honor ulimit -c.
Paul
next prev parent reply other threads:[~2009-04-09 15:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-09 15:05 [Qemu-devel] [PATCH 0/2] linux-user: create coredumps from segfauling target binaries riku.voipio
2009-04-09 15:05 ` [Qemu-devel] [PATCH 1/2] linux-user: implemented ELF coredump support for ARM target riku.voipio
2009-04-09 15:05 ` [Qemu-devel] [PATCH 2/2] linux-user: added x86 and x86_64 support for ELF coredump riku.voipio
2009-04-09 15:27 ` Paul Brook [this message]
2009-04-14 12:52 ` [Qemu-devel] [PATCH 0/2] linux-user: create coredumps from segfauling target binaries 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=200904091627.11381.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).