From: Daniel Jacobowitz <drow@false.org>
To: Mark Mitchell <mark@codesourcery.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: PATCH: Allow for systems that do not define SIGQUIT/SIGPIPE
Date: Wed, 16 Mar 2005 16:52:00 -0000 [thread overview]
Message-ID: <20050316165213.GA6764@nevyn.them.org> (raw)
In-Reply-To: <4238641D.70403@codesourcery.com>
On Wed, Mar 16, 2005 at 08:51:41AM -0800, Mark Mitchell wrote:
> Daniel Jacobowitz wrote:
> >On Wed, Mar 16, 2005 at 08:33:03AM -0800, Mark Mitchell wrote:
> >
> >>Windows does not have SIGQUIT or SIGPIPE.
> >>
> >>Tested on x86_64-unknown-linux-gnu.
> >>
> >>OK?
> >
> >
> >You should probably #ifdef out handle_sigquit and its prototype also,
> >or GCC will warn about it. Right? See the example for SIGWINCH.
>
> Actually, GCC doesn't warn because handle_sigquit references itself. :-)
>
> I'll make that change; OK, assuming it builds?
Yes, is ok.
--
Daniel Jacobowitz
CodeSourcery, LLC
next prev parent reply other threads:[~2005-03-16 16:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-16 16:33 Mark Mitchell
2005-03-16 16:43 ` Daniel Jacobowitz
2005-03-16 16:51 ` Mark Mitchell
2005-03-16 16:52 ` Daniel Jacobowitz [this message]
2005-03-16 17:08 ` Mark Mitchell
2005-03-16 16:53 ` Mark Mitchell
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=20050316165213.GA6764@nevyn.them.org \
--to=drow@false.org \
--cc=gdb-patches@sources.redhat.com \
--cc=mark@codesourcery.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