This is the mail archive of the gdb@sourceware.org mailing list for the GDB project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: Exposing inferior_created in Python

From: Phil Muldoon <pmuldoon at redhat dot com>
To: Gareth McMullin <gareth at blacksphere dot co dot nz>
Cc: gdb at sourceware dot org
Date: Thu, 14 Mar 2013 09:43:23 +0000
Subject: Re: Exposing inferior_created in Python
References: <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

Follow-Ups:
- Re: Exposing inferior_created in Python
  - From: Gareth McMullin

References:
- Exposing inferior_created in Python
  - From: Gareth McMullin

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]