Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Aditya Kamath <Aditya.Kamath1@ibm.com>
To: Simon Marchi <simon.marchi@polymtl.ca>,
	Ulrich Weigand <Ulrich.Weigand@de.ibm.com>,
	Aditya Vidyadhar Kamath <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>
Subject: RE: [PATCH v3] Remove stale pre-AIX-7.2 compatibility guards
Date: Mon, 5 Oct 2026 11:39:23 +0000	[thread overview]
Message-ID: <DSWPR15MB319817778407962E14077B2553D6962@DSWPR15MB319817.namprd15.prod.outlook.com> (raw)
In-Reply-To: <14ef0431-f930-4b03-a186-87b866c0fa06@polymtl.ca>

[-- Attachment #1: Type: text/plain, Size: 2041 bytes --]

Hi Simon and Ulrich,

Thank you for the feedback for this patch series. Please see my comments. Addressing the same I am sending a 4 patch v4 series.


>> On this page I see:
>>
>>     For ptracex or ptrace64: If the debuggee is a 32-bit process, the
>>     options that refer to GPRs or SPRs fail with errno = EIO
>>
>> And I see that in the patch, you call ptrace64 to read registers
>> (PTT_READ_GPRS) for 32 bit processes.  How does that work?
>
> I think Simon is correct here.  For GPRS access, I understand only
> the following options are supported:
>
> ptrace: 32- or 64-bit GDB, 32-bit inferior
> ptracex: 32-bit GDB, 64-bit inferior
> ptrace64: 64-bit GDB, 64-bit inferior
>
> As I understand, the current set of indirections is intended to
> cover that space - for a 32-bit inferior, you call ptrace, and
> for a 64-bit inferior you call either ptracex or ptrace64,
> depending on whether GDB is built as 64-bit.
>Ideally, we wouldn't just guess.  Do you run the testsuite on AIX?  If
>so, you should be able to run it in a mode that builds the test programs
>as 32-bit programs.  For example:

  > $ make check RUNTESTFLAGS='--target_board "unix/-m32"

Yes, I missed this in the documentation. Ulrich and you are right. Appreciate the same for correcting me. I have addressed this and ran the test cases in 32 bit and 64-bit mode on AIX to make sure the changes are functionally correct.

>> Why do you think we can simplify this?  I guess we could make
>> possibly make the assumption that GDB itself is always built
>> as 64-bit these days, but then we still have to select between
>> ptrace and ptrace64 at the least …

>I think that requiring GDB to be built as 64-bit program would be
>reasonable (if so, you should add a static check in the source for that).

Yes, from GDB - 13 we are building GDB on AIX as 64-bit application only. We can adjust the code now with this information. I have done some clean up due to this.

Have a nice day ahead.

Thanks and regards,
Aditya.

[-- Attachment #2: Type: text/html, Size: 4242 bytes --]

  reply	other threads:[~2026-10-05 11:39 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-22  4:52 Aditya Vidyadhar Kamath
2026-09-22 19:58 ` Simon Marchi
2026-09-23 12:53   ` Ulrich Weigand
2026-09-23 13:40     ` Simon Marchi
2026-10-05 11:39       ` Aditya Kamath [this message]
2026-09-22 20:35 ` 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=DSWPR15MB319817778407962E14077B2553D6962@DSWPR15MB319817.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=sangamesh.swamy@in.ibm.com \
    --cc=simon.marchi@polymtl.ca \
    --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