public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "luis.machado at linaro dot org" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug corefiles/27909] New: MTE fixes and MTE corefile support Date: Tue, 25 May 2021 10:45:21 +0000 [thread overview] Message-ID: <bug-27909-4717@http.sourceware.org/bugzilla/> (raw) https://sourceware.org/bugzilla/show_bug.cgi?id=27909 Bug ID: 27909 Summary: MTE fixes and MTE corefile support Product: gdb Version: HEAD Status: NEW Severity: normal Priority: P2 Component: corefiles Assignee: unassigned at sourceware dot org Reporter: luis.machado at linaro dot org Target Milestone: 11.1 Host: aarch64-linux-gnu Target: aarch64-linux-gnu Build: aarch64-linux-gnu There are 4 patches I'd like to push for the GDB 11 release, listed below: "[AArch64] Sanitize the address before working with allocation tags" (Approved) https://sourceware.org/pipermail/gdb-patches/2021-May/178970.html "Fix printing of non pointer types when memory tagging is enabled" (Pending reviews) https://sourceware.org/pipermail/gdb-patches/2021-May/178971.html "Update the core file architecture if a target description is present" (Pending reviews) https://sourceware.org/pipermail/gdb-patches/2021-May/178972.html "[AArch64] MTE corefile support" (Under review) https://sourceware.org/pipermail/gdb-patches/2021-May/178973.html -- You are receiving this mail because: You are on the CC list for the bug.
next reply other threads:[~2021-05-25 10:45 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-05-25 10:45 luis.machado at linaro dot org [this message] 2021-06-25 12:18 ` [Bug corefiles/27909] " luis.machado at linaro dot org 2021-06-26 18:37 ` brobecker at gnat dot com 2021-07-22 12:41 ` luis.machado at linaro dot org 2021-08-02 11:59 ` luis.machado at linaro 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-27909-4717@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: linkBe 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).