Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Pedro Alves <palves@redhat.com>
Cc: tom@tromey.com, gdb-patches@sourceware.org
Subject: Re: [PATCH] Readline: Cleanup some warnings
Date: Thu, 21 Mar 2019 18:30:00 -0000	[thread overview]
Message-ID: <83va0ct71i.fsf@gnu.org> (raw)
In-Reply-To: <3e691193-19c4-056f-eeb5-7837a7e956b3@redhat.com> (message from	Pedro Alves on Thu, 21 Mar 2019 17:31:07 +0000)

> Cc: tom@tromey.com, gdb-patches@sourceware.org
> From: Pedro Alves <palves@redhat.com>
> Date: Thu, 21 Mar 2019 17:31:07 +0000
> 
> So that means that the readline hack in mingw-hdep.c:
> 
>   /* With multi-threaded SIGINT handling, there is a race between the
>      readline signal handler and GDB.  It may still be in
>      rl_prep_terminal in another thread.  Do not return until it is
>      done; we can check the state here because we never longjmp from
>      signal handlers on Windows.  */
>   while (RL_ISSTATE (RL_STATE_SIGHANDLER))
>     Sleep (1);
> 
> with new-enough readline, is no longer doing anything, since the while
> loop's condition is always false.
> 
> However, there's another question that needs answering: what are we going to
> do if even after upgrading our readline version, someone builds gdb against
> the system readline, and the system readline happens to be an older version
> that still depends on this or some other readline hack?  We'll silently
> regress.  I think that we need to document the minimum readline version
> somewhere (gdb/README?), and have something (configure?) enforce it.
> (There's a RL_READLINE_VERSION symbol.)

SGTM, thanks for digging into this.


      reply	other threads:[~2019-03-21 18:30 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-30  8:57 Alan Hayward
2019-01-31  7:59 ` Joel Brobecker
2019-01-31 10:02   ` Alan Hayward
2019-01-31 17:24     ` Alan Hayward
     [not found]       ` <20190201080533.GA31043@adacore.com>
2019-02-01 12:47         ` Tom Tromey
2019-02-01 18:54           ` Philippe Waroquiers
2019-02-06 19:56             ` Pedro Alves
2019-03-17 17:30               ` Tom Tromey
2019-03-17 18:35                 ` Eli Zaretskii
     [not found]                   ` <87imwex333.fsf@tromey.com>
2019-03-19 18:37                     ` Eli Zaretskii
2019-03-19 19:02                     ` Pedro Alves
2019-03-19 19:04                       ` Pedro Alves
2019-03-19 20:14                       ` Eli Zaretskii
2019-03-20  8:55                         ` Eli Zaretskii
2019-03-20 15:46                         ` Pedro Alves
2019-03-20 15:50                           ` Pedro Alves
2019-03-20 17:39                           ` Eli Zaretskii
2019-03-20 17:50                             ` Pedro Alves
2019-03-20 18:01                               ` Eli Zaretskii
2019-03-20 18:28                                 ` Pedro Alves
2019-03-21 17:31                           ` Pedro Alves
2019-03-21 18:30                             ` Eli Zaretskii [this message]

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=83va0ct71i.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=gdb-patches@sourceware.org \
    --cc=palves@redhat.com \
    --cc=tom@tromey.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