From: Tom Tromey <tromey@redhat.com>
To: Pedro Alves <alves.ped@gmail.com>
Cc: Doug Evans <dje@google.com>, Stan Shebs <stanshebs@earthlink.net>,
Eli Zaretskii <eliz@gnu.org>,
gdb-patches@sourceware.org
Subject: Re: [PATCH] Add extra 'info os' information types for Linux (trunk and 7.4)
Date: Mon, 02 Jan 2012 19:41:00 -0000 [thread overview]
Message-ID: <m3ipktnb8y.fsf@fleche.redhat.com> (raw)
In-Reply-To: <4F020332.90308@gmail.com> (Pedro Alves's message of "Mon, 02 Jan 2012 19:19:14 +0000")
>>>>> "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
next prev parent reply other threads:[~2012-01-02 19:41 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-12 18:29 [PATCH] Add extra 'info os' information types for Linux Kwok Cheung Yeung
2011-10-21 23:38 ` Tom Tromey
2011-11-23 18:00 ` Kwok Cheung Yeung
2011-12-27 4:56 ` [PATCH] Add extra 'info os' information types for Linux (trunk and 7.4) Stan Shebs
2011-12-27 9:32 ` Eli Zaretskii
2011-12-27 21:30 ` Mark Kettenis
2011-12-27 23:23 ` Eli Zaretskii
2011-12-28 20:48 ` Mark Kettenis
2011-12-28 0:05 ` Stan Shebs
2011-12-28 3:51 ` Joel Brobecker
2011-12-28 6:02 ` Eli Zaretskii
2012-01-02 12:08 ` Pedro Alves
2012-01-02 12:35 ` Eli Zaretskii
2012-01-02 19:31 ` Pedro Alves
2012-01-03 3:05 ` Joel Brobecker
2012-01-02 18:15 ` Doug Evans
2012-01-02 19:19 ` Pedro Alves
2012-01-02 19:41 ` Tom Tromey [this message]
2011-12-29 20:34 ` Doug Evans
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=m3ipktnb8y.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=alves.ped@gmail.com \
--cc=dje@google.com \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=stanshebs@earthlink.net \
/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