public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Ulrich Weigand <Ulrich.Weigand@de.ibm.com>
To: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>,
	Aditya Kamath1 <Aditya.Kamath1@ibm.com>
Cc: Sangamesh Mallayya <sangamesh.swamy@in.ibm.com>
Subject: Re: [RFC] Using all three fields of ptid and handling thread events from rs6000-aix-nat.c
Date: Tue, 16 Apr 2024 08:52:24 +0000	[thread overview]
Message-ID: <a67c86cdd19de6d25824789d1e93920fd0fab3f5.camel@de.ibm.com> (raw)
In-Reply-To: <CH2PR15MB3544A54C0069F64093476A2BD6092@CH2PR15MB3544.namprd15.prod.outlook.com>

Aditya Kamath1 <Aditya.Kamath1@ibm.com> wrote:

>But in AIX, in sync_threadlist () despite having the code we miss the bus.
>If we observe the sync_threadlists () code our pcount and gcount remain the
>same despite the threads exiting resulting in, we not capturing the exit.

As John already mentioned, I think the main question is why sync_threadlists
doesn't appear to correct update the thread list.  What is the list of threads
it receives from the OS here?  What is supposed to happen according to the
AIX interface specification?

>1: Move the kernel thread handling part to rs6000-aix-nat.c by using all the
>three fields in ptid i.e. pid, lwp and tid, so we can be in sync with Linux
>both in terms of event handling and UI display. [As Ulrich mentions here]

While I still agree this would be useful to do, I don't see how it would
address the problem you're currently seeing.

Bye,
Ulrich


      parent reply	other threads:[~2024-04-16  8:52 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-15 14:37 Aditya Kamath1
2024-04-15 17:36 ` John Baldwin
2024-04-17 10:36   ` Aditya Kamath1
2024-04-17 18:48     ` Ulrich Weigand
2024-04-20 20:25     ` John Baldwin
2024-04-16  8:52 ` Ulrich Weigand [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=a67c86cdd19de6d25824789d1e93920fd0fab3f5.camel@de.ibm.com \
    --to=ulrich.weigand@de.ibm.com \
    --cc=Aditya.Kamath1@ibm.com \
    --cc=gdb-patches@sourceware.org \
    --cc=sangamesh.swamy@in.ibm.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).