public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "jan.kratochvil at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug tui/14584] Cannot scroll the cmd window in TUI mode
Date: Fri, 14 Sep 2012 19:37:00 -0000	[thread overview]
Message-ID: <bug-14584-4717-kQnSo6MGrt@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-14584-4717@http.sourceware.org/bugzilla/>

http://sourceware.org/bugzilla/show_bug.cgi?id=14584

Jan Kratochvil <jan.kratochvil at redhat dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |jan.kratochvil at redhat
                   |                            |dot com

--- Comment #1 from Jan Kratochvil <jan.kratochvil at redhat dot com> 2012-09-14 19:36:26 UTC ---
(In reply to comment #0)
> but the log fails to report the commands from which the output was generated

set trace-commands on


Otherwise you are right that readline library does not provide any real
terminal, it cares only about the current line.  GDB uses 'set pagination on'
so that no output is accidentally lost but what is scrolled away is really
lost. Maybe you would prefer some other front end besides TUI:
  http://sourceware.org/gdb/wiki/GDB_Front_Ends

-- 
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.


  parent reply	other threads:[~2012-09-14 19:37 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-14 19:11 [Bug tui/14584] New: Scrolling does not work " byron at hawkinssoftware dot net
2012-09-14 19:18 ` [Bug tui/14584] Cannot scroll the cmd window " byron at hawkinssoftware dot net
2012-09-14 19:37 ` jan.kratochvil at redhat dot com [this message]
2012-09-14 20:07 ` byron at hawkinssoftware dot net
2012-09-14 20:07 ` byron at hawkinssoftware dot net
2012-09-14 20:08 ` byron at hawkinssoftware dot net
2015-07-03 22:42 ` patrick at parcs dot ath.cx

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=bug-14584-4717-kQnSo6MGrt@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=gdb-prs@sourceware.org \
    /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).