This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [PATCH] Add extra 'info os' information types for Linux (trunk and 7.4)
- From: Tom Tromey <tromey at redhat dot com>
- To: Pedro Alves <alves dot ped at gmail dot com>
- Cc: Doug Evans <dje at google dot com>, Stan Shebs <stanshebs at earthlink dot net>, Eli Zaretskii <eliz at gnu dot org>, gdb-patches at sourceware dot org
- Date: Mon, 02 Jan 2012 12:41:01 -0700
- Subject: Re: [PATCH] Add extra 'info os' information types for Linux (trunk and 7.4)
- References: <4E95DC58.7030805@codesourcery.com> <m3lisedpv0.fsf@fleche.redhat.com> <4ECD3496.1070609@codesourcery.com> <4EF9497B.9020501@earthlink.net> <E1RfQXH-0004RB-1H@fencepost.gnu.org> <4EFA54FF.1080307@earthlink.net> <4F019E45.5010906@gmail.com> <CADPb22Q4iutX_pXs=nw9_FhQLiEGYux8bcwATqRbF5ZK4M2CUg@mail.gmail.com> <4F020332.90308@gmail.com>
>>>>> "Pedro" == Pedro Alves <alves.ped@gmail.com> writes:
Pedro> Certainly. "info os" is all about structured data. Whether exposed as
Pedro> raw xml or as some other pre-parsed structured form is arguable; it
Pedro> could be said to fit fit in the general theme of exposing mi
Pedro> structures to python as well? Not sure.
Recently I have been thinking that emit_stop_event (emitting normal
stops as Python events) should probably call bpstat_print and expose the
resulting information as fields of the event. This in turn would need a
new ui-out that can create Python objects.
If there is sufficient need we can generalize this idea.
There's a PR about this already.
Tom