Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Joel Brobecker <brobecker@adacore.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [RFC] control-c handling on Windows...
Date: Sun, 11 May 2008 13:46:00 -0000	[thread overview]
Message-ID: <umymyklkh.fsf@gnu.org> (raw)
In-Reply-To: <20080510180010.GF28890@adacore.com>

> Date: Sat, 10 May 2008 11:00:10 -0700
> From: Joel Brobecker <brobecker@adacore.com>
> 
>     void
>     quit (void)
>     {
>     #ifdef __MSDOS__
>       /* No steenking SIGINT will ever be coming our way when the
>          program is resumed.  Don't lie.  */
>       fatal ("Quit");
>     #else
>       if (job_control
>           /* If there is no terminal switching for this target, then we can't
>              possibly get screwed by the lack of job control.  */
>           || current_target.to_terminal_ours == NULL)
>         fatal ("Quit");
>       else
>         fatal ("Quit (expect signal SIGINT when the program is resumed)");
>     #endif
>     }
> 
> Not sure when __MSDOS__ is defined

It's defined in the DJGPP build of GDB.  This bogus "expect SIGINT"
message was bugging me for years, until I #ifdef'ed it away.


  reply	other threads:[~2008-05-10 19:26 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-08  9:46 Joel Brobecker
2008-05-10  4:34 ` Christopher Faylor
2008-05-10 13:10   ` Joel Brobecker
2008-05-10 15:31     ` Christopher Faylor
2008-05-10 22:28       ` Joel Brobecker
2008-05-11  5:30         ` Christopher Faylor
2008-05-11 13:31         ` Joel Brobecker
2008-05-11 13:46           ` Eli Zaretskii [this message]
2008-05-11 13:58           ` Christopher Faylor
2008-05-11 21:26             ` Joel Brobecker
2008-05-17 11:38               ` Christopher Faylor
2008-05-21  0:34                 ` Joel Brobecker
2008-05-21  3:19                   ` Christopher Faylor

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=umymyklkh.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=brobecker@adacore.com \
    --cc=gdb-patches@sourceware.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