From: Tom Tromey <tom@tromey.com>
To: Simon Farre via Gdb-patches <gdb-patches@sourceware.org>
Subject: Re: [PATCH v2] gdb/Python: Added ThreadExitedEvent
Date: Mon, 18 Apr 2022 07:58:36 -0600 [thread overview]
Message-ID: <87h76qxzlf.fsf@tromey.com> (raw)
In-Reply-To: <CACx6OkxE2VQUMneD+JM6-86WXrt7yJ3HPOsToo6Wf7ARtgUJOQ@mail.gmail.com> (Simon Farre via Gdb-patches's message of "Mon, 18 Apr 2022 11:38:14 +0200")
>>>>> "Simon" == Simon Farre via Gdb-patches <gdb-patches@sourceware.org> writes:
Simon> I was unaware of the LWP not being cross-platform, perhaps this
Simon> field should be removed then? Or is there some relevant/similar
Simon> info on other platforms that can be returned here (and by that
Simon> logic, also change the attribute to a name that logically could
Simon> explain the attribute in a cross-platform manner?)
Which fields in a ptid are used depends on the target.
There's been some attempt to regularize this across targets, but TBH I
don't know if that's been completed or not. (And despite having done
some of this, I also forgot what the rule is :-)
Anyway I wouldn't worry about it. Emitting the thread object alone
would probably be better. And, if someone references the LWP and it
isn't set, it will just be 0.
Tom
next prev parent reply other threads:[~2022-04-18 13:58 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-12 9:03 Simon Farre
2022-04-15 18:06 ` Tom Tromey
2022-04-18 10:30 ` Simon Farre
2022-04-18 13:57 ` Tom Tromey
2022-04-15 19:46 ` Eli Zaretskii
2022-04-18 9:38 ` Simon Farre
2022-04-18 9:41 ` Eli Zaretskii
2022-04-18 13:58 ` Tom Tromey [this message]
2022-04-18 16:19 ` Pedro Alves
2022-04-19 11:42 ` Simon Farre
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=87h76qxzlf.fsf@tromey.com \
--to=tom@tromey.com \
--cc=gdb-patches@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).