From: Tom Tromey <tromey@redhat.com>
To: Michael Eager <eager@eagerm.com>
Cc: "gdb-patches\@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: [PATCH] PR14291: KeyboardInterrupt not caught for Python output
Date: Mon, 25 Jun 2012 15:26:00 -0000 [thread overview]
Message-ID: <87mx3rct1r.fsf@fleche.redhat.com> (raw)
In-Reply-To: <4FE85A77.70809@eagerm.com> (Michael Eager's message of "Mon, 25 Jun 2012 05:32:55 -0700")
>>>>> "Michael" == Michael Eager <eager@eagerm.com> writes:
Michael> 2012-06-25 Michael Eager <eager@eagercon.com>
Michael> * python/python.c (gdbpy_write): Check for interrupted
Michael> output.
Ok.
Tom
next prev parent reply other threads:[~2012-06-25 15:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-25 12:33 Michael Eager
2012-06-25 15:26 ` Tom Tromey [this message]
2012-06-25 16:54 ` Michael Eager
2012-06-27 13:37 ` Tom Tromey
2012-06-27 14:06 ` Michael Eager
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=87mx3rct1r.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=eager@eagerm.com \
--cc=gdb-patches@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