From: Freddie Chopin <freddie_chopin@op.pl>
To: Liviu Ionescu <ilg@livius.net>
Cc: gdb@sourceware.org, openocd-devel <openocd-devel@lists.sourceforge.net>
Subject: Re: [OpenOCD-devel] Python API for supplying thread information?
Date: Wed, 22 Mar 2017 11:46:00 -0000 [thread overview]
Message-ID: <1490183183.1242.18.camel@op.pl> (raw)
In-Reply-To: <8FB0BA0B-F013-48A6-965B-AEF4B69610EC@livius.net>
On Wed, 2017-03-22 at 13:01 +0200, Liviu Ionescu wrote:
> even if this is possible, it does not cover all debugging tools
> (increasing in popularity right now, at least for FreeRTOS) that
> might need to introspect the RTOS, for example Eclipse plug-ins to
> display the status of semaphores, queues, memory allocators, etc.
The tools you mentioned clearly don't use OpenOCD's RTOS support or
GDB's thread info for that anyway, as neither provides any info about
things you mentioned (semaphores, queues, allocators, ...). So that
hypothetical change that I suggested neither prevents nor enables them
to do that. And if these tools do that now, they do that by directly
accessing target memory via GDB, so no special support for anything
like that is required.
Regards,
FCh
next prev parent reply other threads:[~2017-03-22 11:46 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 [this message]
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
[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=1490183183.1242.18.camel@op.pl \
--to=freddie_chopin@op.pl \
--cc=gdb@sourceware.org \
--cc=ilg@livius.net \
--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