This is the mail archive of the
gdb@sourceware.org
mailing list for the GDB project.
Re: [OpenOCD-devel] Python API for supplying thread information?
- From: Freddie Chopin <freddie_chopin at op dot pl>
- To: Liviu Ionescu <ilg at livius dot net>
- Cc: gdb at sourceware dot org, openocd-devel <openocd-devel at lists dot sourceforge dot net>
- Date: Wed, 22 Mar 2017 12:46:23 +0100
- Subject: Re: [OpenOCD-devel] Python API for supplying thread information?
- Authentication-results: sourceware.org; auth=none
- References: <1490175792.1242.7.camel@op.pl> <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