From: Aditya Vidyadhar Kamath <ADITYA.VIDYADHAR.KAMATH@ibm.com>
To: Joel Brobecker via Gdb-patches <gdb-patches@sourceware.org>,
Simon Marchi <simon.marchi@polymtl.ca>
Subject: Query while adding fork feature - AIX
Date: Tue, 21 Jun 2022 16:29:37 +0000 [thread overview]
Message-ID: <BN8PR15MB286708717DC8511A5A4A0607B5B39@BN8PR15MB2867.namprd15.prod.outlook.com> (raw)
Hi all,
Currently I am working on adding fork multi-inferior support for AIX. I was stuck at an issue and thought to reach out to the community.
Let's say we have a child process created from a fork event as well as added a thread to the child process inferior thread list. Yet when the switch is made to the child process a SIGHUP signal comes, or PC register is not available. What can be the possible reasons and what are the things a developer must handle when a child process is added as new inferior [Assuming users will switch into the child].
The answer to this question will help me out in figuring out where I am possibly going wrong or missing out on some useful information I should keep in mind.
Hoping for a response.
Have a nice day ahead.
Thanking you,
Regards,
Aditya.
reply other threads:[~2022-06-21 16:29 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=BN8PR15MB286708717DC8511A5A4A0607B5B39@BN8PR15MB2867.namprd15.prod.outlook.com \
--to=aditya.vidyadhar.kamath@ibm.com \
--cc=gdb-patches@sourceware.org \
--cc=simon.marchi@polymtl.ca \
/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).