This is the mail archive of the
archer@sourceware.org
mailing list for the Archer project.
Re: plan for python inferiors, threads, and events
- From: Tom Tromey <tromey at redhat dot com>
- To: Pedro Alves <pedro at codesourcery dot com>
- Cc: archer at sourceware dot org, Paul Pluzhnikov <ppluzhnikov at google dot com>
- Date: Mon, 05 Jan 2009 16:56:00 -0700
- Subject: Re: plan for python inferiors, threads, and events
- References: <m31vwd9pk2.fsf@fleche.redhat.com><8ac60eac0812121152n2a5c991n6ff1dc515154f7f@mail.gmail.com><8ac60eac0812301514l315687c0ue4940a40e3777188@mail.gmail.com><200812310351.10413.pedro@codesourcery.com>
- Reply-to: Tom Tromey <tromey at redhat dot com>
>>>>> "Pedro" == Pedro Alves <pedro@codesourcery.com> writes:
>> On Tuesday 30 December 2008 23:14:15, Paul Pluzhnikov wrote:
>> So I figured I'd just ask gdb.threads() for a list of threads, search
>> our live threads list for a matching thread, and print its name.
Pedro> [if/when considering reimplementing a special "info threads" in
Pedro> python is overkill]
Yeah, it kind of is overkill. OTOH, it is more convenient to go this
route, because it lets one write app- or organization-specific
commands without hacking gdb itself. Scripts are simpler to deploy.
Pedro> Sounds like you wanted a hook similar to target_extra_thread_info, but
Pedro> in the app/scripting domain.
Thanks for the tip :)
Tom