From: Phil Muldoon <pmuldoon@redhat.com>
To: Freddie Chopin <freddie_chopin@op.pl>
Cc: gdb@sourceware.org, openocd-devel@lists.sourceforge.net
Subject: Re: Python API for supplying thread information?
Date: Wed, 22 Mar 2017 15:37:00 -0000 [thread overview]
Message-ID: <4b310e40-3f39-feed-6134-d2cfe68c4423@redhat.com> (raw)
In-Reply-To: <1490175792.1242.7.camel@op.pl>
On 22/03/17 09:43, Freddie Chopin wrote:
> Hello!
>
> The idea I'm asking about is related to the Pretty Printing API in
> Python, which allows one to extend behaviour of GDB completely on
> "client side" - there's absolutely no need to modify any component of
> the toolchain to print your own types in any way you like.
>
> It would be really great if something like this existed for _supplying_
> thread information to GDB. I'm not talking about the Python API to
> _query_ GDB about threads.
> ( https://sourceware.org/gdb/onlinedocs/gdb/Threads-In-Python.html ).
(Resending to include correct CC's/To's)
Is it possible? Sure. But without looking at it in any real depth it
would be a major undertaking. GDB does not have the concept of
"Providers", it assembles state from many different sources: kernel,
glibc, libthread_db etc. This state is internally structured and
relevant to GDB and is not really structured to receive arbitrary
input from an API at the moment. It could, but I think it would
require major surgery.
Currently the Scripting API is almost entirely focused with providing
information and not really designed to take information. You have
information providers APIs and data decorators APIs.
My advice would be to undertake a study to estimate the work needed.
Cheers
Phil
next prev parent reply other threads:[~2017-03-22 15:37 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-22 9:43 Freddie Chopin
2017-03-22 11:01 ` [OpenOCD-devel] " Liviu Ionescu
2017-03-22 11:46 ` Freddie Chopin
2017-03-22 17:23 ` Pierre-Marie de Rodat
2017-03-22 17:52 ` Freddie Chopin
2017-03-23 9:23 ` Pierre-Marie de Rodat
2017-03-23 16:50 ` Freddie Chopin
2017-03-23 18:08 ` Liviu Ionescu
2017-03-31 10:55 ` Gary Benson
2017-03-22 15:32 ` Phil Muldoon
2017-03-22 15:37 ` Phil Muldoon [this message]
2017-03-22 16:20 ` Freddie Chopin
2017-03-23 11:34 ` Yao Qi
2017-03-23 14:33 ` [OpenOCD-devel] " Duane Ellis
2017-03-26 14:11 ` Freddie Chopin
2017-03-23 16:41 ` Freddie Chopin
[not found] ` <CADQtY4AdhK73Gva2TYo4VDaTsY3Z33MtrJVLc-OwXwD6R5OqtQ@mail.gmail.com>
2017-03-26 14:02 ` [OpenOCD-devel] " Freddie Chopin
2017-03-22 21:51 ` Gareth McMullin
2017-03-23 16:44 ` Freddie Chopin
[not found] ` <220810f4-9843-d898-6947-e7eeeed3a1ed@daniel-krebs.net>
2017-03-23 16:56 ` [OpenOCD-devel] " Freddie Chopin
[not found] ` <CADQtY4BBxGdOg=DNqZYigA2G8-MVi5bvbbccfh8Vy_KEx-U+ug@mail.gmail.com>
2017-03-26 13:58 ` Freddie Chopin
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=4b310e40-3f39-feed-6134-d2cfe68c4423@redhat.com \
--to=pmuldoon@redhat.com \
--cc=freddie_chopin@op.pl \
--cc=gdb@sourceware.org \
--cc=openocd-devel@lists.sourceforge.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