From: Aditya Kamath1 <Aditya.Kamath1@ibm.com>
To: Ulrich Weigand <Ulrich.Weigand@de.ibm.com>,
"akamath996@gmail.com" <akamath996@gmail.com>,
"tom@tromey.com" <tom@tromey.com>
Cc: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>,
Sangamesh Mallayya <sangamesh.swamy@in.ibm.com>,
"jhb@freebsd.org" <jhb@freebsd.org>
Subject: Re: [PATCH v5] Fix AIX thread exit events not being reported and UI to show kernel thread ID.
Date: Thu, 9 May 2024 05:44:01 +0000 [thread overview]
Message-ID: <BY5PR15MB3540C1882FBA240DF2A2930DD6E62@BY5PR15MB3540.namprd15.prod.outlook.com> (raw)
In-Reply-To: <77774246617d84a793bdae6750e37310ef6bb94a.camel@de.ibm.com>
[-- Attachment #1: Type: text/plain, Size: 917 bytes --]
Thank you Ulrich and community members.
From: Ulrich Weigand <Ulrich.Weigand@de.ibm.com>
Date: Wednesday, 8 May 2024 at 8:25 PM
To: akamath996@gmail.com <akamath996@gmail.com>, tom@tromey.com <tom@tromey.com>
Cc: gdb-patches@sourceware.org <gdb-patches@sourceware.org>, Aditya Kamath1 <Aditya.Kamath1@ibm.com>, Sangamesh Mallayya <sangamesh.swamy@in.ibm.com>, jhb@freebsd.org <jhb@freebsd.org>
Subject: Re: [PATCH v5] Fix AIX thread exit events not being reported and UI to show kernel thread ID.
Aditya Vidyadhar Kamath <akamath996@gmail.com> wrote:
>In AIX when a thread exits we were not showing that a thread exit event happened
>and GDB continued to keep the terminated threads.
>The reason being in sync_threadlists () the pbuf and gbuf lists remain the same though certain threads exit.
>
>This patch is a fix to the same.
This version is OK. I've applied the patch.
Thanks,
Ulrich
prev parent reply other threads:[~2024-05-09 5:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-03 15:09 Aditya Vidyadhar Kamath
2024-05-03 15:14 ` Aditya Kamath1
2024-05-07 9:57 ` Aditya Kamath1
2024-05-08 14:55 ` Ulrich Weigand
2024-05-09 5:44 ` Aditya Kamath1 [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=BY5PR15MB3540C1882FBA240DF2A2930DD6E62@BY5PR15MB3540.namprd15.prod.outlook.com \
--to=aditya.kamath1@ibm.com \
--cc=Ulrich.Weigand@de.ibm.com \
--cc=akamath996@gmail.com \
--cc=gdb-patches@sourceware.org \
--cc=jhb@freebsd.org \
--cc=sangamesh.swamy@in.ibm.com \
--cc=tom@tromey.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).