From: Tom Tromey <tromey@redhat.com>
To: Pedro Alves <palves@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH 1/2] remote.c: Use the ptid.lwp field to store remote thread ids rather than ptid.tid.
Date: Wed, 12 Feb 2014 16:56:00 -0000 [thread overview]
Message-ID: <87a9dwuv5h.fsf@fleche.redhat.com> (raw)
In-Reply-To: <1392214020-21478-2-git-send-email-palves@redhat.com> (Pedro Alves's message of "Wed, 12 Feb 2014 14:06:59 +0000")
>>>>> "Pedro" == Pedro Alves <palves@redhat.com> writes:
Pedro> I believe that on the GDB side too, it's best that we standardize on
Pedro> process_stratum targets using the ptid.lwp field to store thread ids.
Pedro> The idea being leave the ptid.tid field free for any thread_stratum
Pedro> target that might want to sit on top.
Thanks for doing this.
Pedro> Because remote.c is currently using ptid.tid, we can't make gdbserver
Pedro> and gdb share bits of remote-specific code that manipulates ptids.
Pedro reminded me that the functions in question are read_ptid and
write_ptid.
Tom
next prev parent reply other threads:[~2014-02-12 16:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-12 14:07 [PATCH 0/2] remote.c: ptid.tid -> ptid.lwp Pedro Alves
2014-02-12 14:07 ` [PATCH 2/2] common/ptid.h: Mention that process_stratum targets should prefer ptid.lwp Pedro Alves
2014-02-12 14:07 ` [PATCH 1/2] remote.c: Use the ptid.lwp field to store remote thread ids rather than ptid.tid Pedro Alves
2014-02-12 16:56 ` Tom Tromey [this message]
2014-02-12 16:58 ` Pedro Alves
2014-02-12 18:09 ` Doug Evans
2014-02-19 19:09 ` [PATCH 0/2] remote.c: ptid.tid -> ptid.lwp Pedro Alves
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=87a9dwuv5h.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=palves@redhat.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