From: Mark Mitchell <mark@codesourcery.com>
To: Daniel Jacobowitz <drow@false.org>
Cc: Eli Zaretskii <eliz@gnu.org>,
bug-readline@gnu.org, gdb-patches@sources.redhat.com
Subject: Re: PATCH: Readline on MinGW
Date: Thu, 28 Apr 2005 20:45:00 -0000 [thread overview]
Message-ID: <42714B6F.1030009@codesourcery.com> (raw)
In-Reply-To: <20050428201215.GA14846@nevyn.them.org>
Daniel Jacobowitz wrote:
> On Thu, Apr 28, 2005 at 11:06:45PM +0300, Eli Zaretskii wrote:
>
>>I am not sure `raise' is a 100% compatible replacement for `kill',
>>since the latter really delivers a signal, and so is subject to rules
>>regarding blocked signals, while `raise' simlpy calls the signal
>>handler and AFAIK is not specified to observe blocked signals.
>>
>>So I suggest to use `raise' only on systems, such as MinGW, which lack
>>`kill', not everywhere.
>
>
> Could you give me a reference for this? POSIX disagrees:
>
> http://www.opengroup.org/onlinepubs/009695399/functions/raise.html
Yes, I looked at that (and the GNU/Linux, and Solaris manual pages)
before making that change. But, I'm happy to change the code to check
for "kill", and use "raise" only if unavailable, as Eli suggests, if
that's necessary.
Eli, just to be clear, you said you "support" the patches I posted (with
this exception). I'm interpreting that as "I hope they go into upstream
readline", rather than as "it's OK to check these patches into the GDB
repository." If you actually meant the latter, let me know. :-)
--
Mark Mitchell
CodeSourcery, LLC
mark@codesourcery.com
(916) 791-8304
next prev parent reply other threads:[~2005-04-28 20:45 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-28 6:53 Mark Mitchell
2005-04-28 20:09 ` Eli Zaretskii
2005-04-28 20:12 ` Daniel Jacobowitz
2005-04-28 20:45 ` Mark Mitchell [this message]
2005-04-28 21:02 ` Chet Ramey
2005-04-29 0:44 ` Mark Mitchell
2005-04-29 7:31 ` Eli Zaretskii
2005-04-29 16:10 ` Christopher Faylor
2005-04-29 1:51 ` Mark Mitchell
2005-04-28 21:02 ` Eli Zaretskii
2005-04-28 20:50 ` Eli Zaretskii
2005-04-28 21:17 ` Daniel Jacobowitz
2005-04-28 22:13 ` Andreas Schwab
2005-04-29 6:59 ` Eli Zaretskii
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=42714B6F.1030009@codesourcery.com \
--to=mark@codesourcery.com \
--cc=bug-readline@gnu.org \
--cc=drow@false.org \
--cc=eliz@gnu.org \
--cc=gdb-patches@sources.redhat.com \
/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