From: Nicholas_Karagas@cirilium.com
To: insight@sourceware.cygnus.com
Subject: prompt in console window
Date: Wed, 14 Jun 2000 13:02:00 -0000 [thread overview]
Message-ID: <OF14E7EA77.DC16752A-ON072568FE.006D40EF@cirilium.com> (raw)
Hello, Insight gurus...
I've recently come across a problem using the console window in Insight.
In ordinary GDB, if the number of lines printed exceeds the 'height'
parameter, then the debugger will issue the prompt '---Type <return> to
continue, or q <return> to quit---'. However, this apparently doesn't work
in the Insight console, as the call to readline (readline.c:337) from
prompt_for_continue (utils.c:1619) always returns 0x0, and never shows the
prompt in the console window. I imagine that this is because readline
expects everything to be going to and from stdout (since it doesn't require
a stream as a parameter). Is there a quick fix for this that doesn't
involve fiddling with readline, and therefore binutils (I think that's
where it lives)? Thanks in advance.
Nicholas Karagas
Associate Software Engineer
Cirilium Corporation
Tempe, AZ
(480) 317-1144
next reply other threads:[~2000-06-14 13:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-06-14 13:02 Nicholas_Karagas [this message]
2000-06-15 6:11 ` Keith Seitz
2000-06-15 10:29 ` Jim Ingham
2000-06-15 10:42 ` Keith Seitz
2000-06-15 10:11 Nicholas_Karagas
2000-06-15 10:35 ` Jim Ingham
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=OF14E7EA77.DC16752A-ON072568FE.006D40EF@cirilium.com \
--to=nicholas_karagas@cirilium.com \
--cc=insight@sourceware.cygnus.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).