Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Tom Tromey <tromey@redhat.com>
To: Khoo Yit Phang <khooyp@cs.umd.edu>
Cc: Pedro Alves <palves@redhat.com>,
	GDB Patches <gdb-patches@sourceware.org>
Subject: Re: python-interactive, and quitting gdb pagination
Date: Mon, 10 Sep 2012 20:07:00 -0000	[thread overview]
Message-ID: <87zk4xbq1f.fsf@fleche.redhat.com> (raw)
In-Reply-To: <AB38DA2F-50A2-40DF-A39E-1E38384BC620@cs.umd.edu> (Khoo Yit	Phang's message of "Thu, 23 Aug 2012 13:31:43 -0400")

>>>>> "Yit" == Khoo Yit Phang <khooyp@cs.umd.edu> writes:

Yit> Hmm, this happens because quitting from GDB's pager happens to raise
Yit> the same error reason, RETURN_QUIT, as typing Ctrl-C, i.e., quitting
Yit> from the pager looks exactly like Ctrl-C. I'm not quite sure what the
Yit> best way to fix this is; perhaps disable the pager while in Python?
Yit> Python's "help" runs a pager too, but I think it's disabled because
Yit> stdin/stdout is redirected through GDB. Or alternatively, perhaps
Yit> somehow differentiate quitting from the pager or quitting from Ctrl-C,
Yit> e.g., with a different error.message?

Having Python use the pager is kind of a feature.  It lets one write gdb
commands in Python that work like other gdb commands.

I suppose we could provide a way to bypass the pager.
Doing so during python-interactive might make sense, though I am not
sure.

Tom


      reply	other threads:[~2012-09-10 20:07 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-23 17:07 Pedro Alves
2012-08-23 17:32 ` Khoo Yit Phang
2012-09-10 20:07   ` Tom Tromey [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=87zk4xbq1f.fsf@fleche.redhat.com \
    --to=tromey@redhat.com \
    --cc=gdb-patches@sourceware.org \
    --cc=khooyp@cs.umd.edu \
    --cc=palves@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