From: Simon Marchi <simark@simark.ca>
To: Ulrich Weigand <Ulrich.Weigand@de.ibm.com>,
Aditya Kamath1 <Aditya.Kamath1@ibm.com>,
"gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Cc: Sangamesh Mallayya <sangamesh.swamy@in.ibm.com>
Subject: Re: [PATCH] Enable multi process debugging for AIX
Date: Mon, 22 Aug 2022 10:19:29 -0400 [thread overview]
Message-ID: <2d4bf02f-5ad8-8cf1-a4dd-40d7d2d4dacb@simark.ca> (raw)
In-Reply-To: <b5f0a3ba2f59d9ed28ef2f0ae4b9c99a50565cfc.camel@de.ibm.com>
> As to this:
> +# define AIX_FORK_EVENT 0x57e
>
> It would be much preferable to use the official names for these
> constants. For example, the document you mention here:
>
>> More about this can be read in the document
>> https://www.ibm.com/docs/en/aix/7.2?topic=p-ptrace-ptracex-ptrace64-
> subroutine
>
> talks about:
> W_SFWTED
> Process stopped during execution of the fork subroutine.
>
> Is this the 0x57e event? If so, we should call it W_SFWTED in GDB as
> well, and not some made-up name.
>
> It would be great if you could find the official names for all the
> other "magic" constants like 0x7f, 0x17f, 0x137f etc. as well.
Is there no system header file that provides them?
Simon
next prev parent reply other threads:[~2022-08-22 14:19 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-19 15:53 Aditya Kamath1
2022-07-19 18:51 ` Simon Marchi
2022-07-22 16:56 ` Aditya Kamath1
2022-08-18 18:59 ` Aditya Kamath1
2022-08-21 17:15 ` Aditya Kamath1
2022-08-22 13:25 ` Ulrich Weigand
2022-08-22 14:19 ` Simon Marchi [this message]
2022-08-23 6:52 ` Aditya Kamath1
2022-10-19 10:57 ` Aditya Kamath1
2022-10-19 10:57 ` Aditya Kamath1
2022-10-28 10:59 ` Ulrich Weigand
2022-11-01 13:55 ` Aditya Kamath1
2022-11-02 8:56 ` Ulrich Weigand
2022-11-10 10:39 ` Aditya Kamath1
2022-11-14 18:24 ` Ulrich Weigand
2022-11-15 7:13 ` Aditya Kamath1
2022-11-15 10:53 ` Ulrich Weigand
2022-11-15 12:01 ` Aditya Kamath1
2022-11-15 12:43 ` Ulrich Weigand
2022-11-15 18:13 ` Aditya Kamath1
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=2d4bf02f-5ad8-8cf1-a4dd-40d7d2d4dacb@simark.ca \
--to=simark@simark.ca \
--cc=Aditya.Kamath1@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).