From: Jeff Dike <jdike@addtoit.com>
To: blaisorblade_spam@yahoo.it
Cc: user-mode-linux-devel@lists.sourceforge.net
Subject: [uml-devel] Re: [patch 2/2] add-SIGPROF-get-set_signals
Date: Sun, 12 Sep 2004 23:32:39 -0400 [thread overview]
Message-ID: <20040913033239.GA13207@ccure.user-mode-linux.org> (raw)
In-Reply-To: <20040912182629.3FEC49F37@zion.localdomain>
On Sun, Sep 12, 2004 at 08:26:29PM +0200, blaisorblade_spam@yahoo.it wrote:
> {
> sigset_t mask;
> + sigset_t old_mask;
> int ret;
Weren't you just complaining about stack consumption? Do you know how
big a sigset_t is?
(gdb) p sizeof(sigset_t)
$1 = 128
I went to a reasonable amount of trouble to get that function to only
use one sigset_t and now you are proposing to add the old one back.
Fix the patch and I'll put it in.
Also, if you're going to fix something, send a patch which does
nothing but make the fix, and save whatever cleanups you want to make
for a differet patch.
Jeff
-------------------------------------------------------
This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170
Project Admins to receive an Apple iPod Mini FREE for your judgement on
who ports your project to Linux PPC the best. Sponsored by IBM.
Deadline: Sept. 13. Go here: http://sf.net/ppc_contest.php
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel
next prev parent reply other threads:[~2004-09-13 2:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-12 18:26 [uml-devel] [patch 2/2] add-SIGPROF-get-set_signals blaisorblade_spam
2004-09-13 3:32 ` Jeff Dike [this message]
2004-09-13 18:12 ` [uml-devel] " BlaisorBlade
2004-09-13 22:15 ` Jeff Dike
2004-09-14 19:26 ` Jeff Dike
2004-09-17 18:52 ` BlaisorBlade
2004-09-18 0:45 ` Jeff Dike
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=20040913033239.GA13207@ccure.user-mode-linux.org \
--to=jdike@addtoit.com \
--cc=blaisorblade_spam@yahoo.it \
--cc=user-mode-linux-devel@lists.sourceforge.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.