public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "vries at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug tdep/31418] New: [gdb/tdep, arm] $tpidruro unavailable Date: Tue, 27 Feb 2024 16:16:30 +0000 [thread overview] Message-ID: <bug-31418-4717@http.sourceware.org/bugzilla/> (raw) https://sourceware.org/bugzilla/show_bug.cgi?id=31418 Bug ID: 31418 Summary: [gdb/tdep, arm] $tpidruro unavailable Product: gdb Version: HEAD Status: NEW Severity: normal Priority: P2 Component: tdep Assignee: unassigned at sourceware dot org Reporter: vries at gcc dot gnu.org Target Milestone: --- As earlier reported here ( https://sourceware.org/pipermail/gdb-patches/2024-February/206644.html ): ... $ gcc hello.c $ gdb -q -batch a.out -ex start -ex 'p $tpidruro' Temporary breakpoint 1 at 0x512 Temporary breakpoint 1, 0xaaaaa512 in main () $1 = <unavailable> ... This is on a pinebook, with 64-bit kernel and 32-bit userland. -- You are receiving this mail because: You are on the CC list for the bug.
next reply other threads:[~2024-02-27 16:16 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-02-27 16:16 vries at gcc dot gnu.org [this message] 2024-02-27 16:17 ` [Bug tdep/31418] " vries at gcc dot gnu.org 2024-02-27 21:50 ` thiago.bauermann at linaro dot org 2024-02-29 15:33 ` cvs-commit at gcc dot gnu.org 2024-03-04 15:18 ` vries 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-31418-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).