public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
From: Mark Kettenis <kettenis@chello.nl>
To: gdb@sources.redhat.com
Subject: completion.exp and the pager
Date: Sun, 17 Aug 2003 12:38:00 -0000	[thread overview]
Message-ID: <200308171238.h7HCcZDJ003071@elgar.kettenis.dyndns.org> (raw)

Folks,

On various FreeBSD 5.x systems I get a few failures in completion.exp.
The first failure is:

  FAIL: gdb.base/completion.exp: (timeout) complete (2) 'p 'a'

If I look at gdb.log, it's clear what's happening.  FreeBSD has quite
a few symbols in libc that start with an 'a'.  Defenitely more than
can be listed on a 24-line terminal.  The pager kicks in and the test
gets a timeout:

  acl_dup                  aio_error                authdes_create
  acl_free                 aio_read                 authdes_getucred
  acl_from_text            aio_return               authdes_lock
  --More--FAIL: gdb.base/completion.exp: (timeout) complete (2) 'p 'a'
  ^G^MESC[K^Macl_get_entry            aio_suspend              authdes_ops_lock
  acl_get_fd               aio_waitcomplete         authdes_pk_seccreate

This isn't our normal pager (the test does a "set height 0"), but
readline's completion pager.  However, we don't synchronize GDB's and
readline's idea of the size of our terminal.  I think we should do
this.

The readline library has the functions rl_{get|set}_screen_size() to
communicate the size of the terminal.  It's also possible to disable
the completion pager entirely, but that's a bit more cumbersome, since
it has to be done with rl_variable_bind(), and it doesn't seem to be
possible to check the current setting.

I'll see whether I can come up with a patch.

Mark

                 reply	other threads:[~2003-08-17 12:38 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=200308171238.h7HCcZDJ003071@elgar.kettenis.dyndns.org \
    --to=kettenis@chello.nl \
    --cc=gdb@sources.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).