From: Simon Marchi <simark@simark.ca>
To: Aditya Vidyadhar Kamath <ADITYA.VIDYADHAR.KAMATH@ibm.com>,
Ulrich Weigand <Ulrich.Weigand@de.ibm.com>,
Joel Brobecker via Gdb-patches <gdb-patches@sourceware.org>
Cc: Sangamesh Mallayya <sangamesh.swamy@in.ibm.com>
Subject: Re: Fw: RE: [PATCH] Fix assert pid != 0 assertion failure in AIX
Date: Thu, 7 Jul 2022 09:56:20 -0400 [thread overview]
Message-ID: <bb54bca7-794c-f207-72fe-4b4e4ec1ae86@simark.ca> (raw)
In-Reply-To: <BN8PR15MB2867D767070CA2A62BF96939B5839@BN8PR15MB2867.namprd15.prod.outlook.com>
On 2022-07-07 04:27, Aditya Vidyadhar Kamath wrote:
> Hi Simon,
>
> I appreciate your patience to read our explanations, understand and suggest us the right path.
>
> I was not aware of minus_one_ptid. I thought since pid will be -1, if a child process in not fetched to send ptid_t(pid).. That change you made looks good. Thank you for your guidance for someone new in this project.
>
> Changing all function parameters will help us in our fork patch coming soon. So that change also looks to good to eliminate depending on inferior_ptid.
>
> Multi thread programs are not seen even from my end. Yes, there is some work for multi thread case. Will work on it finding out a possible solution sometime next week.
>
> Having said that, we can push the changes so that folks using AIX will not see the assertion failure for simple programs soon. It will be great if it can be done.
>
> Have a great day ahead,
Ok, thanks, I pushed the patch to the master branch.
Simon
prev parent reply other threads:[~2022-07-07 13:56 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-29 6:58 [PATCH] Use current_inferior ()->pid for AIX Aditya Vidyadhar Kamath
2022-03-29 13:01 ` Simon Marchi
2022-03-30 13:04 ` Aditya Vidyadhar Kamath
2022-04-05 12:15 ` Aditya Vidyadhar Kamath
2022-04-05 12:47 ` Simon Marchi
2022-04-12 13:32 ` Aditya Vidyadhar Kamath
2022-04-18 6:33 ` Aditya Vidyadhar Kamath
2022-04-21 11:41 ` Aditya Vidyadhar Kamath
2022-04-21 14:51 ` Simon Marchi
[not found] ` <BN8PR15MB2867D6D625DD0B353C99D3A3B5DD9@BN8PR15MB2867.namprd15.prod.outlook.com>
2022-05-30 12:45 ` Simon Marchi
2022-06-10 14:47 ` Aditya Vidyadhar Kamath
2022-06-15 4:03 ` Aditya Vidyadhar Kamath
2022-06-23 20:40 ` Aditya Vidyadhar Kamath
2022-06-27 12:55 ` Fw: " Aditya Vidyadhar Kamath
2022-06-27 15:11 ` Simon Marchi
2022-07-04 19:28 ` Simon Marchi
2022-07-06 4:25 ` Fw: RE: [PATCH] Fix assert pid != 0 assertion failure in AIX Aditya Vidyadhar Kamath
2022-07-06 17:50 ` Simon Marchi
2022-07-07 8:27 ` Aditya Vidyadhar Kamath
2022-07-07 13:56 ` Simon Marchi [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=bb54bca7-794c-f207-72fe-4b4e4ec1ae86@simark.ca \
--to=simark@simark.ca \
--cc=ADITYA.VIDYADHAR.KAMATH@ibm.com \
--cc=Ulrich.Weigand@de.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).