public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "luis.machado at arm dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/28947] GDB does not remove AArch64 pointer signatures before doing memory accesses
Date: Thu, 26 May 2022 08:23:44 +0000	[thread overview]
Message-ID: <bug-28947-4717-II5WNydrCt@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-28947-4717@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=28947

--- Comment #6 from Luis Machado <luis.machado at arm dot com> ---
I see your point about making it a bit more convenient for the user. It's just
that we're dealing with best-effort cases here, as we don't know some of the
intentions the developer has before going and processing pointers.

It wouldn't be nice to have two distinct behaviors for the debuggers though.

As GDB already removes the (hardcoded) top 8 bits, I'm considering modifying
the hook to actually return a stripped pointer as opposed to letting generic
code remove X number of top bits.

This way we can make sure we output the proper stripped pointer. GDB had an
issue before where it failed to deal with kernel pointers, as it had to
sign-extend them while stripping the top bits.

I'll put something together along with a testcase.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

  parent reply	other threads:[~2022-05-26  8:23 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-07 11:32 [Bug gdb/28947] New: " david.spickett at linaro dot org
2022-03-07 11:45 ` [Bug gdb/28947] " luis.machado at arm dot com
2022-03-07 11:46 ` luis.machado at arm dot com
2022-03-07 13:28 ` luis.machado at arm dot com
2022-05-24  8:04 ` luis.machado at arm dot com
2022-05-24  8:06 ` luis.machado at arm dot com
2022-05-24  9:06 ` david.spickett at linaro dot org
2022-05-26  8:23 ` luis.machado at arm dot com [this message]
2022-09-15  7:58 ` luis.machado at arm dot com
2022-12-16 11:19 ` cvs-commit at gcc dot gnu.org
2022-12-16 11:22 ` luis.machado at arm dot com

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=bug-28947-4717-II5WNydrCt@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=gdb-prs@sourceware.org \
    /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).