Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Doug Evans <xdje42@gmail.com>
To: fei ding <fdingiit@gmail.com>
Cc: gdb <gdb@sourceware.org>
Subject: Re: How to get all threads of a definite process?
Date: Sun, 08 Feb 2015 05:13:00 -0000	[thread overview]
Message-ID: <CAP9bCMQigszFS1QzO99U+-4fsh1mVZmzUp0Fc=c7D6e3iOUpDQ@mail.gmail.com> (raw)
In-Reply-To: <CAGmPkfJXp2Dr97U0dETN84-qkBumxD845XBVrnbYBCD=gW43YA@mail.gmail.com>

On Thu, Feb 5, 2015 at 10:15 PM, fei ding <fdingiit@gmail.com> wrote:
> BTW, I am talking about gdbserver, Thanks
>
> 2015-02-06 14:14 GMT+08:00 fei ding <fdingiit@gmail.com>:
>> Hi, everyone:
>>
>> I want to get all threads of one definite process, and I've found some
>> data structure such as 'all_threads', which is not what I want, i
>> guess. I don't understand the relationship between process and thread,
>> from the gdb-source-code-level (pointers for example),  and I don't
>> understand the meaning of 'ptid_t', does this mean 'process_thread_id'
>> ? and I've found this data's value is not the thread's PID that Linux
>> shell tell me, it just some number like 0 or 1.

You'll need to clarify. ptid_t is a struct of three values,
it is not "just some number like 0 or 1".

>>
>> If you know something about this, please help me. Thanks.

ptid_t is the type gdb uses internally to identify both processes and threads.
Its API is defined in gdb/common/ptid.[ch].

There is ptid_match() which could be given a process ptid for the filter,
and then you just need to iterate over all_threads, e.g. with
for_each_inferior_with_data, for threads that match (IOW for threads
that have the same process id).


      reply	other threads:[~2015-02-08  5:13 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-06  6:14 fei ding
2015-02-06  6:15 ` fei ding
2015-02-08  5:13   ` Doug Evans [this message]

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='CAP9bCMQigszFS1QzO99U+-4fsh1mVZmzUp0Fc=c7D6e3iOUpDQ@mail.gmail.com' \
    --to=xdje42@gmail.com \
    --cc=fdingiit@gmail.com \
    --cc=gdb@sourceware.org \
    /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