Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Freddie Chopin <freddie_chopin@op.pl>
To: Yao Qi <qiyaoltc@gmail.com>
Cc: Phil Muldoon <pmuldoon@redhat.com>,
	gdb@sourceware.org, 	openocd-devel@lists.sourceforge.net
Subject: Re: Python API for supplying thread information?
Date: Thu, 23 Mar 2017 16:41:00 -0000	[thread overview]
Message-ID: <1490287249.1231.3.camel@op.pl> (raw)
In-Reply-To: <86mvccuszh.fsf@gmail.com>

On Thu, 2017-03-23 at 11:34 +0000, Yao Qi wrote:Providing
> thread info isn't just printing thread name and state in "info
> threads".  GDB internally needs thread information too.

But that's all GDB is getting from OpenOCD - thread name (string),
extra info (string) and stack frame (registers).

Unless I'm missing something, which is of course possible (;

Regards,
FCh


  parent reply	other threads:[~2017-03-23 16:41 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 [this message]
     [not found]         ` <CADQtY4AdhK73Gva2TYo4VDaTsY3Z33MtrJVLc-OwXwD6R5OqtQ@mail.gmail.com>
2017-03-26 14:02           ` 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=1490287249.1231.3.camel@op.pl \
    --to=freddie_chopin@op.pl \
    --cc=gdb@sourceware.org \
    --cc=openocd-devel@lists.sourceforge.net \
    --cc=pmuldoon@redhat.com \
    --cc=qiyaoltc@gmail.com \
    /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