From: Freddie Chopin <freddie_chopin@op.pl>
To: Gareth McMullin <gareth@blacksphere.co.nz>
Cc: gdb@sourceware.org, openocd-devel <openocd-devel@lists.sourceforge.net>
Subject: Re: Python API for supplying thread information?
Date: Thu, 23 Mar 2017 16:44:00 -0000 [thread overview]
Message-ID: <1490287437.1231.5.camel@op.pl> (raw)
In-Reply-To: <CAL8qUbrcM=khjNAAs2NgvDcwYZVGbyZduazPqFo=phyZVL3zJQ@mail.gmail.com>
On Thu, 2017-03-23 at 10:50 +1300, Gareth McMullin wrote:
> I am also of the opinion that this would be better achieved as a
> Python extension to GDB.
> A while ago I worked on some Python scripts that fake it in GDB, by
> overriding the `thread`
> and `info threads` CLI commands.
> https://github.com/gsmcmullin/gdb_chibios/blob/master/chibios.py
> (This is for ChibiOS 2 and is not currently maintained.)Â Â It
> obviously
> doesn't work
> with frontends using MI.
I had a crazy idea yesterday, that it should (maybe) be possible to
implement a python "bridge" between GDB and OpenOCD. This script would
open sockets for both ends and generally be transparent to the traffic.
But it could intercept all the GDB packets about threads. This way this
logic could be implemented completely in the script. This seems
promising, but I'm not sure it would be possible to create such bridged
connection between GDB and OpenOCD while intercepting some of the
traffic...
Regards,
FCh
next prev parent reply other threads:[~2017-03-23 16:44 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
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 [this message]
[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=1490287437.1231.5.camel@op.pl \
--to=freddie_chopin@op.pl \
--cc=gareth@blacksphere.co.nz \
--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