From: Phil Muldoon <pmuldoon@redhat.com>
To: Gareth McMullin <gareth@blacksphere.co.nz>
Cc: gdb@sourceware.org
Subject: Re: Exposing inferior_created in Python
Date: Thu, 14 Mar 2013 09:43:00 -0000 [thread overview]
Message-ID: <51419BBB.1030800@redhat.com> (raw)
In-Reply-To: <CAL8qUbr3izTP5U66k_zOfif=cGyZtx5+D1zjgZX4CUNtbCs0HQ@mail.gmail.com>
On 14/03/13 04:18, Gareth McMullin wrote:
> Hi
>
> I'm interested in having the inferior_created observer exposed as a
> Python event
I think it is fine to create event and observers in GDB/Python that
you have identified a need for.
That being said, what do you mean by inferior_created event?
Currently we have observers in the Python API for:
* Breakpoint events
* Continue events.
* Exiting events
* New object file events
* Signal events
* Inferior halting/stopping events
* Thread events
Would the thread event/observer satisfy your use-case? I am pretty
much guessing, though, until you can expand on the inferior_created
case.
Cheers
Phil
next prev parent reply other threads:[~2013-03-14 9:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-14 4:19 Gareth McMullin
2013-03-14 9:43 ` Phil Muldoon [this message]
2013-03-14 11:13 ` Gareth McMullin
2013-03-20 20:40 ` Tom Tromey
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=51419BBB.1030800@redhat.com \
--to=pmuldoon@redhat.com \
--cc=gareth@blacksphere.co.nz \
--cc=gdb@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