Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Simon Marchi <simon.marchi@polymtl.ca>
To: Tom Tromey <tom@tromey.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [RFA 1/3] Add new_inferior, inferior_deleted, and new_thread events
Date: Sat, 09 Sep 2017 16:48:00 -0000	[thread overview]
Message-ID: <7fc7800c8c532e0a290cf4c6ab9882b0@polymtl.ca> (raw)
In-Reply-To: <20170909003353.25883-2-tom@tromey.com>

On 2017-09-09 02:33, Tom Tromey wrote:
> This adds a few new events to gdb's Python layer: new_inferior,
> inferior_deleted, and new_thread.  I wanted to be able to add a
> combined inferior/thread display window to my GUI, and I needed a few
> events to make this work.  This is PR python/15622.

Apart for my comment about documentation, this patch LGTM.

Thanks,

Simon


  parent reply	other threads:[~2017-09-09 16:48 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-09  0:34 [RFA 0/3] add a few Python events Tom Tromey
2017-09-09  0:34 ` [RFA 3/3] Make it simpler to add events to Python Tom Tromey
2017-09-09 14:40   ` Tom Tromey
2017-09-09 17:05   ` Simon Marchi
2017-09-10  0:24     ` Tom Tromey
2017-09-09  0:34 ` [RFA 1/3] Add new_inferior, inferior_deleted, and new_thread events Tom Tromey
2017-09-09  6:55   ` Eli Zaretskii
2017-09-09 16:47     ` Simon Marchi
2017-09-09 20:41       ` Tom Tromey
2017-09-09 21:09         ` Simon Marchi
2017-09-10  0:21       ` Tom Tromey
2017-09-10 19:37         ` Simon Marchi
2017-09-10 21:52           ` Tom Tromey
2017-09-11 11:54             ` Simon Marchi
2017-09-11 14:29               ` Eli Zaretskii
2017-09-09 16:48   ` Simon Marchi [this message]
2017-09-09  0:34 ` [RFA 2/3] Small event ownership clean up in Python layer Tom Tromey
2017-09-09 17:05   ` Simon Marchi

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=7fc7800c8c532e0a290cf4c6ab9882b0@polymtl.ca \
    --to=simon.marchi@polymtl.ca \
    --cc=gdb-patches@sourceware.org \
    --cc=tom@tromey.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