public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "byron at hawkinssoftware dot net" <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 20:08:00 -0000	[thread overview]
Message-ID: <bug-14584-4717-KcfQCVFtva@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-14584-4717@http.sourceware.org/bugzilla/>

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

--- Comment #4 from Byron Hawkins <byron at hawkinssoftware dot net> 2012-09-14 20:07:58 UTC ---
Actually with "set trace-commands on" I can just tail the log. (I searched for
a long time trying to find such a setting and did not come up with anything.)
The graphical interfaces seem to always be missing essential things, like
printing assembly at an arbitrary address, so I will use TUI with logging.

It still seems unfortunate that TUI mode is so convenient, yet destroys the
output. If it would just work the same as GDB without TUI mode, it would be
great.

-- 
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 20:08 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
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 [this message]
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-KcfQCVFtva@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).