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 tdep/30540] [gdb/tdep] AT_RSEQ_FEATURE_SIZE / AT_RSEQ_ALIGN support missing in "info auxv"
Date: Sat, 07 Oct 2023 01:29:31 +0000 [thread overview]
Message-ID: <bug-30540-4717-duMglE3qhC@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-30540-4717@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=30540
--- Comment #3 from cvs-commit at gcc dot gnu.org <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Simon Marchi <simark@sourceware.org>:
https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=7a3bb62d82631ff042525b7115d9e03a7329e7be
commit 7a3bb62d82631ff042525b7115d9e03a7329e7be
Author: Ilya Leoshkevich <iii@linux.ibm.com>
Date: Thu Jun 22 01:03:04 2023 +0200
gdb: support rseq auxvs
Linux kernel commit commit 317c8194e6ae ("rseq: Introduce feature size
and alignment ELF auxiliary vector entries") introduced two new auxvs:
AT_RSEQ_FEATURE_SIZE and AT_RSEQ_ALIGN. Support them in GDB. This
fixes auxv.exp on kernels >= v6.3.
Change-Id: I8966c4d5c73eb7b45de6d410a9b28a6628edad2e
Bug: https://sourceware.org/bugzilla/show_bug.cgi?id=30540
Approved-By: Tom Tromey <tom@tromey.com>
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2023-10-07 1:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-12 7:36 [Bug tdep/30540] New: " vries at gcc dot gnu.org
2023-09-19 17:52 ` [Bug tdep/30540] " tromey at sourceware dot org
2023-10-03 20:34 ` vries at gcc dot gnu.org
2023-10-07 1:29 ` cvs-commit at gcc dot gnu.org [this message]
2023-10-07 13:42 ` tromey at sourceware dot 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-30540-4717-duMglE3qhC@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).