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] Use current_inferior ()->pid for AIX
Date: Mon, 4 Jul 2022 15:28:53 -0400 [thread overview]
Message-ID: <e94ba62c-0437-1365-24e5-26a85837dc54@simark.ca> (raw)
In-Reply-To: <BN8PR15MB286736FF41E2D2D6BCBC7462B5B99@BN8PR15MB2867.namprd15.prod.outlook.com>
On 6/27/22 08:55, Aditya Vidyadhar Kamath via Gdb-patches wrote:
> Hi,
>
> We have worked our way out through the pid!=0 assertion failure.
>
> Currently we also plan to come out soon with the patches for fork support as well in AIX.
>
> It will be great if we could get a review to the patch [Forwarded in this email] whenever you find time.
>
> Have a nice day ahead.
>
> Thanks and regards,
> Aditya
Hi Aditya,
I looked at your patch, and unfortunately I don't understand how it
improves things. In my past messages, I tried to explain that the root
of the problem is that the wait methods code is relying on the entry
value of inferior_ptid, when it shouldn't. I don't see how adding one
more reference to inferior_ptid in rs6000_nat_target::wait helps.
Given your goal is to support forks (and thus multi-process, I
suppose?), try to write the code in the wait method in such a way that
it doesn't rely on the inferior_ptid value or current inferior value on
entry. The typical pattern for the wait methods is that they fetch some
event (using waitpid in your case) and then figure out which inferior
from the inferior list this event applies to.
Simon
next prev parent reply other threads:[~2022-07-04 19:28 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-29 6:58 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 [this message]
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
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=e94ba62c-0437-1365-24e5-26a85837dc54@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).