From: Mark Kettenis <kettenis@chello.nl>
To: schwab@suse.de
Cc: tromey@redhat.com, fnasser@redhat.com, ezannoni@redhat.com,
gdb-patches@sources.redhat.com
Subject: Re: [RFA/TESTSUITE]: readline tests
Date: Fri, 16 Aug 2002 17:47:00 -0000 [thread overview]
Message-ID: <200208170047.g7H0lYmB015007@elgar.kettenis.dyndns.org> (raw)
In-Reply-To: <je3ctezk3p.fsf@sykes.suse.de> (message from Andreas Schwab on Fri, 16 Aug 2002 21:20:26 +0200)
From: Andreas Schwab <schwab@suse.de>
Date: Fri, 16 Aug 2002 21:20:26 +0200
User-Agent: Gnus/5.090007 (Oort Gnus v0.07) Emacs/21.3.50 (ia64-suse-linux)
Content-Type: text/plain; charset=iso-8859-1
Tom Tromey <tromey@redhat.com> writes:
|> I think this means that sending C-o didn't cause an operate-and-get-next.
|> The subsequent problems are caused by this.
Note that C-o is typically also allocated to the tty flush (DISCARD)
character. Since readline does not reset the IEXTEN flag the flush
character may still be intercepted by the tty driver even in non-canonical
input.
Yup, that's what's happening. After
$ stty discard ^Y
operate-and-get-next works fine. So we should either reset the IEXTEN
or set DISCARD to _POSIX_VDISABLE, either in readline or GDB. I'm
inclined to make the attached patch to readline, since something
similar is already done for LNEXT. Should I submit it to the readline
maintainer?
PS Something strange is still happening. Some operate-and-get-next
tests still fail when a .gdb_history file is present in the current
directory that has more than 254 lines. If no .gdb_history file is
present or if it contains less than 255 lines, the tests succeed.
Unfortunately a test that gets run earlier produces just that; a
.gdb_history file with 257 lines. Anyway, it seems that I've found a
bug in the history code. I'll see if I can find it.
Index: rltty.c
===================================================================
RCS file: /cvs/src/src/readline/rltty.c,v
retrieving revision 1.5
diff -u -p -r1.5 rltty.c
--- rltty.c 8 Jan 2001 14:57:30 -0000 1.5
+++ rltty.c 17 Aug 2002 00:25:48 -0000
@@ -598,6 +598,10 @@ prepare_terminal_settings (meta_flag, ot
be necessary. */
#if defined (TERMIOS_TTY_DRIVER) && defined (_POSIX_VDISABLE)
+#if defined (VDISCARD)
+ tiop->c_cc[VDISCARD] = _POSIX_VDISABLE;
+#endif
+
#if defined (VLNEXT)
tiop->c_cc[VLNEXT] = _POSIX_VDISABLE;
#endif
prev parent reply other threads:[~2002-08-17 0:47 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-24 12:08 Tom Tromey
2002-08-13 13:10 ` Fernando Nasser
2002-08-13 13:13 ` Elena Zannoni
2002-08-13 13:23 ` Fernando Nasser
2002-08-13 15:10 ` Tom Tromey
2002-08-15 11:19 ` Mark Kettenis
2002-08-16 10:54 ` Tom Tromey
2002-08-16 12:20 ` Andreas Schwab
2002-08-16 17:47 ` Mark Kettenis [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=200208170047.g7H0lYmB015007@elgar.kettenis.dyndns.org \
--to=kettenis@chello.nl \
--cc=ezannoni@redhat.com \
--cc=fnasser@redhat.com \
--cc=gdb-patches@sources.redhat.com \
--cc=schwab@suse.de \
--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