Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Kevin Pouget <kevin.pouget@gmail.com>
To: Tom Tromey <tromey@redhat.com>
Cc: Khoo Yit Phang <khooyp@cs.umd.edu>, gdb-patches@sourceware.org
Subject: Re: [PATCH 4/4]: Enable readline under "python"
Date: Thu, 23 Aug 2012 11:21:00 -0000	[thread overview]
Message-ID: <CAPftXUK9vA038CifUs8HqzXfxruLbxG1o0M4kvcb7pNPYCGmgg@mail.gmail.com> (raw)
In-Reply-To: <87393esnv9.fsf@fleche.redhat.com>

On Wed, Aug 22, 2012 at 9:55 PM, Tom Tromey <tromey@redhat.com> wrote:
>
> >>>>> "Yit" == Khoo Yit Phang <khooyp@cs.umd.edu> writes:
>
> Yit> Hi,
> Yit> I've updated my Python/GDB readline patch for the new SIGINT handling
> Yit> patch that you've just checked in, Tom. The only change is that
> Yit> there's no longer any need to swap SIGINT handlers. If it's alright,
> Yit> I'll check it in.
>
> It is ok.  Thanks!
>
> Tom

hello,

it might be a stupid question, and I didn't take time to read the
patch ... but how do we exit from this `python-interactive` command?
exit() and quit() just kill the entire GDB ... If I didn't miss
something obvious, it might worth adding a line in the documentation.


(and just a detail, in the gdb/ChangeLog of this patch, I think that this line:
> * doc/gdb.texinfo (Python Commands): Document the new commands.
is supposted to go to doc/ChangeLog


and by the way this readline and interactive prompt is a *very* cool
job, GDB/Python will become really more intuitive!


Thanks,

Kevin


  reply	other threads:[~2012-08-23 11:21 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-16 21:04 Khoo Yit Phang
2012-07-25 17:38 ` Tom Tromey
2012-08-22 19:39   ` Khoo Yit Phang
2012-08-22 19:55     ` Tom Tromey
2012-08-23 11:21       ` Kevin Pouget [this message]
2012-08-23 13:04         ` Khoo Yit Phang
2012-08-23 13:15           ` Kevin Pouget
2012-08-24  1:42         ` Khoo Yit Phang
2012-08-24  8:55           ` Pedro Alves

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=CAPftXUK9vA038CifUs8HqzXfxruLbxG1o0M4kvcb7pNPYCGmgg@mail.gmail.com \
    --to=kevin.pouget@gmail.com \
    --cc=gdb-patches@sourceware.org \
    --cc=khooyp@cs.umd.edu \
    --cc=tromey@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