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/31531] New: [aarch64,sme] gdb doesn't restore the vg register properly when dealing with streaming functions Date: Fri, 22 Mar 2024 15:00:42 +0000 [thread overview] Message-ID: <bug-31531-4717@http.sourceware.org/bugzilla/> (raw) https://sourceware.org/bugzilla/show_bug.cgi?id=31531 Bug ID: 31531 Summary: [aarch64,sme] gdb doesn't restore the vg register properly when dealing with streaming functions Product: gdb Version: HEAD Status: NEW Severity: normal Priority: P2 Component: gdb Assignee: unassigned at sourceware dot org Reporter: luis.machado at arm dot com Target Milestone: --- When gdb is dealing with streaming functions, the vg register (the vector length) will change its value to that of the svg register. If the vg and svg registers differ, when gdb attempts to unwind from a streaming function through a non-streaming function, the frame with the non-streaming function will contain the wrong vg register value. If we have variables tied to the vg register value in the non-streaming frame, gdb will display their contents incorrectly. gdb needs to recognize vg was saved and follow the CFI rules to restore it. -- You are receiving this mail because: You are on the CC list for the bug.
next reply other threads:[~2024-03-22 15:00 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-03-22 15:00 luis.machado at arm dot com [this message] 2024-03-22 15:02 ` [Bug tdep/31531] " 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-31531-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).