Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: Ralf Corsepius <ralf.corsepius@rtems.org>
Cc: Joel Brobecker <brobecker@adacore.com>,
	gdb@sourceware.org,         Tom Tromey <tromey@redhat.com>
Subject: Re: GDB 6.8.92 available for testing
Date: Thu, 01 Oct 2009 10:09:00 -0000	[thread overview]
Message-ID: <20091001100900.GA16002@host0.dyn.jankratochvil.net> (raw)
In-Reply-To: <4AC41F44.1040502@rtems.org>

On Thu, 01 Oct 2009 05:17:24 +0200, Ralf Corsepius wrote:
> --enable-system-readline also is still broken (Jan, please submit
> your gdb-readline-6.0.patch you have applied to Fedora's gdb).

* I do not consider it appropriate for FSF GDB as the Fedora patch is just
  a hack, GDB should not make references to readline internal variables.

* FSF GDB does build with the default options.  Dependencies on external
  libraries are a task of distro vendors and the distros already contain GDB
  patches on their own.

And the fix is not straightforward as trying to avoid this internal variable
reference one has to face the echoing behavior which I find brokwn already
even with the bundled readline and the existing internal variable reference:

Standard terminal readline:
$ gdb -q
(gdb) <enter>
(gdb) 

TUI behavior:
$ gdb -q --tui
(gdb) <enter - nothing happens, it clears the same line>

The TUI window should emulate the standard terminal window so the behavior
should be the same, shouldn't it?  But I do not have a fix for this first
part.


Regards,
Jan


  parent reply	other threads:[~2009-10-01 10:09 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-30 20:48 Joel Brobecker
2009-10-01  3:17 ` Ralf Corsepius
2009-10-01  8:59   ` Andreas Schwab
2009-10-01  9:35     ` Pierre Muller
2009-10-01  9:42       ` Andreas Schwab
2009-10-01 12:11         ` Ralf Corsepius
2009-10-01 13:10           ` Jan Kratochvil
2009-10-02 15:40             ` Tom Tromey
2009-10-02 17:26               ` Jan Kratochvil
2009-10-01 10:09   ` Jan Kratochvil [this message]
2009-10-01 11:20     ` Ralf Corsepius
2009-10-01 18:16       ` Joel Brobecker
2009-10-02  2:46         ` Ralf Corsepius
2009-10-02 15:39     ` Tom Tromey
2009-10-02 17:28       ` Jan Kratochvil
2009-10-01 17:07   ` Joel Brobecker
2009-10-01 17:21     ` Ralf Corsepius
2009-10-01 17:35       ` Mark Kettenis
2009-10-01 18:27         ` Joel Brobecker
2009-10-01 18:37           ` Mark Kettenis
2009-10-01 20:22             ` Eli Zaretskii
2009-10-01 18:40           ` Paul Pluzhnikov
2009-10-01 18:25       ` Joel Brobecker
2009-10-02 15:48       ` Tom Tromey
2009-10-02 16:57         ` Ralf Corsepius
2009-10-02 17:27           ` Tom Tromey
2009-10-02 18:04             ` Mark Kettenis
2009-10-02 18:15               ` Joel Brobecker
2009-10-02 18:24                 ` Mark Kettenis
2009-10-02 18:38                   ` Jan Kratochvil
2009-10-02 21:46                     ` Tom Tromey
2009-10-02 22:00                       ` Jan Kratochvil
2009-10-02 15:35   ` Tom Tromey
2009-10-01 12:02 ` Pierre Muller
2009-10-01 17:56   ` Joel Brobecker
2009-10-01 21:22     ` [RFA] more fixes to testsuite (was RE: GDB 6.8.92 available for testing) Pierre Muller
2009-10-01 21:28       ` Joel Brobecker

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=20091001100900.GA16002@host0.dyn.jankratochvil.net \
    --to=jan.kratochvil@redhat.com \
    --cc=brobecker@adacore.com \
    --cc=gdb@sourceware.org \
    --cc=ralf.corsepius@rtems.org \
    --cc=tromey@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