Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Tom Tromey <tom@tromey.com>
To: Pedro Alves <palves@redhat.com>
Cc: "gdb-patches\@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: [PATCH] Readline: Cleanup some warnings
Date: Sun, 17 Mar 2019 17:30:00 -0000	[thread overview]
Message-ID: <87wokxtnlt.fsf@tromey.com> (raw)
In-Reply-To: <310315f8-62ab-2eff-042f-9f2ae9de07da@redhat.com> (Pedro Alves's	message of "Wed, 6 Feb 2019 19:56:35 +0000")

>>>>> "Pedro" == Pedro Alves <palves@redhat.com> writes:

Pedro> See the description in commit 4a11f2065906, which was later
Pedro> reverted:

Thanks.  I've pulled that into my readline upgrade series.

I have to disable guile to get this test to work.  When guile is
enabled, there's an early SEGV in the garbage collector -- it is
expected and is caught by the GC, but this test case doesn't know how to
cope.

I'm looking now at importing readline 8.0.

I still don't really know what to do about the readline-related hack in
the mingw gdb_select.  I'd like to remove it, but I can't test it and I
don't know whether it's still needed.

Tom


  reply	other threads:[~2019-03-17 17: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 [this message]
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

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=87wokxtnlt.fsf@tromey.com \
    --to=tom@tromey.com \
    --cc=gdb-patches@sourceware.org \
    --cc=palves@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