From: Ulrich Hecht <uli@suse.de>
To: "Arnaud Patard (Rtp)" <arnaud.patard@rtp-net.org>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] linux-user and signal handling
Date: Thu, 18 Jun 2009 18:08:14 +0200 [thread overview]
Message-ID: <200906181808.15408.uli@suse.de> (raw)
In-Reply-To: <200906181735.09280.uli@suse.de>
On Thursday 18 June 2009, Ulrich Hecht wrote:
> And the culprit indeed
> seems to be edf8e2af1453ce56c72b2f25a745e3734177a05d
Specifically, it's the part in force_sig() that sets the core limit to 0
to prevent a core dump of qemu itself that causes the wrong core bit.
Remove it, and the test passes. No idea how to fix that properly,
though.
CU
Uli
--
Heute ist
- Tag der Aussiedlung (in Ägypten)
SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg)
next prev parent reply other threads:[~2009-06-18 16:08 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-18 11:56 [Qemu-devel] linux-user and signal handling Arnaud Patard
2009-06-18 13:26 ` Ulrich Hecht
2009-06-18 15:17 ` Arnaud Patard
2009-06-18 15:35 ` Ulrich Hecht
2009-06-18 16:08 ` Ulrich Hecht [this message]
2009-06-18 16:27 ` Arnaud Patard
2009-06-18 17:14 ` Daniel Jacobowitz
2009-06-18 18:45 ` Riku Voipio
2009-06-18 19:40 ` Arnaud Patard
2009-06-19 8:08 ` 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=200906181808.15408.uli@suse.de \
--to=uli@suse.de \
--cc=arnaud.patard@rtp-net.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).