public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "shivam98.tkg at gmail dot com" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug gdb/28371] gdb: watchpoint for local variable doesn't work on RISC-V Date: Tue, 26 Oct 2021 10:18:45 +0000 [thread overview] Message-ID: <bug-28371-4717-zy530z3i7f@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-28371-4717@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=28371 shivam98.tkg at gmail dot com <shivam98.tkg at gmail dot com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |WONTFIX --- Comment #15 from shivam98.tkg at gmail dot com <shivam98.tkg at gmail dot com> --- I close it here now and might open a new issue to track hardware watchpoint support in gdb. -- You are receiving this mail because: You are on the CC list for the bug.
prev parent reply other threads:[~2021-10-26 10:18 UTC|newest] Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-09-22 7:00 [Bug gdb/28371] New: " shivam98.tkg at gmail dot com 2021-09-23 4:03 ` [Bug gdb/28371] " shivam98.tkg at gmail dot com 2021-09-24 22:51 ` wilson at gcc dot gnu.org 2021-09-26 18:17 ` shivam98.tkg at gmail dot com 2021-09-26 18:39 ` shivam98.tkg at gmail dot com 2021-09-28 2:07 ` evandro.menezes at sifive dot com 2021-09-29 21:28 ` wilson at gcc dot gnu.org 2021-09-29 21:42 ` jrtc27 at jrtc27 dot com 2021-09-29 21:42 ` jrtc27 at jrtc27 dot com 2021-09-30 9:56 ` shivam98.tkg at gmail dot com 2021-09-30 9:57 ` shivam98.tkg at gmail dot com 2021-09-30 9:59 ` shivam98.tkg at gmail dot com 2021-09-30 10:02 ` shivam98.tkg at gmail dot com 2021-09-30 10:35 ` schwab@linux-m68k.org 2021-10-01 19:48 ` wilson at gcc dot gnu.org 2021-10-11 10:11 ` shivam98.tkg at gmail dot com 2021-10-26 6:03 ` shivam98.tkg at gmail dot com 2021-10-26 10:18 ` shivam98.tkg at gmail dot com [this message]
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-28371-4717-zy530z3i7f@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).