From: Tom Tromey <tromey@redhat.com>
To: Pedro Alves <palves@redhat.com>
Cc: Maxime Coste <frrrwww@gmail.com>, gdb-patches@sourceware.org
Subject: Re: [PATCH 1/3] Add a select_frame_reason enum parameter to select_frame
Date: Fri, 10 May 2013 19:50:00 -0000 [thread overview]
Message-ID: <87mws2fwd8.fsf@fleche.redhat.com> (raw)
In-Reply-To: <5187E029.8070008@redhat.com> (Pedro Alves's message of "Mon, 06 May 2013 17:54:01 +0100")
>>>>> "Pedro" == Pedro Alves <palves@redhat.com> writes:
Pedro> If we limit frame change notifications to user frame changes
Pedro> (CLI up/down/frame and MI equivalents), then these issues
Pedro> with stops would be non-issues by design...
That sounds like a reasonable plan to me.
Tom
next prev parent reply other threads:[~2013-05-10 19:50 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-26 21:07 Add a python event registry for selected frame changes Maxime Coste
2013-04-26 21:09 ` [PATCH 1/3] Add a select_frame_reason enum parameter to select_frame Maxime Coste
2013-04-30 11:05 ` Tom Tromey
2013-04-30 11:53 ` Joel Brobecker
2013-05-06 16:54 ` Pedro Alves
2013-05-10 19:50 ` Tom Tromey [this message]
2013-05-14 13:23 ` Maxime Coste
2013-04-26 21:10 ` [PATCH 2/3] Add a frame_changed observer Maxime Coste
2013-04-30 10:51 ` Tom Tromey
2013-04-27 7:55 ` [PATCH 3/3] Add a gdb.events.frame_change event registry Maxime Coste
2013-04-30 11:07 ` Tom Tromey
2013-04-30 11:09 ` Tom Tromey
2013-04-30 10:53 ` Add a python event registry for selected frame changes Tom Tromey
2013-04-30 23:29 ` Maxime Coste
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=87mws2fwd8.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=frrrwww@gmail.com \
--cc=gdb-patches@sourceware.org \
--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