public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug server/31511] gdbserver doesn't work on x32
Date: Mon, 25 Mar 2024 17:19:03 +0000	[thread overview]
Message-ID: <bug-31511-4717-XsNbVthdEH@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-31511-4717@http.sourceware.org/bugzilla/>

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

--- Comment #4 from Sourceware Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Andrew Burgess <aburgess@sourceware.org>:

https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=efba976d9713a92b4507ccfef2257e4589da2798

commit efba976d9713a92b4507ccfef2257e4589da2798
Author: Andrew Burgess <aburgess@redhat.com>
Date:   Sat Mar 23 16:17:36 2024 +0000

    gdb/arch: assert that X86_XSTATE_MPX is not set for x32

    While trying to merge this commit:

      commit 4bb20a6244b7091a9a7a2ae35dfbd7e8db27550a
      Date:   Wed Mar 20 04:13:18 2024 -0700

          gdbserver: Clear X86_XSTATE_MPX bits in xcr0 on x32

    With this patch series of mine:

     
https://inbox.sourceware.org/gdb-patches/cover.1706801009.git.aburgess@redhat.com

    I worried that there could be other paths that could result in an xcr0
    value that has X86_XSTATE_MPX set in x32 mode.  As everyone eventually
    calls amd64_create_target_description to build their target
    description, I figured we could assert in here that if X86_XSTATE_MPX
    is set then we should not be an x32 target, this should uncover any
    other bugs in this area.

    I'm not currently able to build/run any x32 binaries, so I have no way
    to test this.

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

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

  parent reply	other threads:[~2024-03-25 17:19 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-19 15:21 [Bug server/31511] New: " hjl.tools at gmail dot com
2024-03-20 13:24 ` [Bug server/31511] " tromey at sourceware dot org
2024-03-21 19:45 ` cvs-commit at gcc dot gnu.org
2024-03-21 20:42 ` tromey at sourceware dot org
2024-03-25 17:19 ` cvs-commit at gcc dot gnu.org [this message]
2024-05-07 16:07 ` cvs-commit at gcc dot gnu.org

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-31511-4717-XsNbVthdEH@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).