public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "jeremy.bennett at embecosm dot com" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug breakpoints/15902] New: Hardware watchpoints on remote targets do not automatically fall back to software watchpoints Date: Tue, 27 Aug 2013 17:04:00 -0000 [thread overview] Message-ID: <bug-15902-4717@http.sourceware.org/bugzilla/> (raw) https://sourceware.org/bugzilla/show_bug.cgi?id=15902 Bug ID: 15902 Summary: Hardware watchpoints on remote targets do not automatically fall back to software watchpoints Product: gdb Version: HEAD Status: NEW Severity: normal Priority: P2 Component: breakpoints Assignee: unassigned at sourceware dot org Reporter: jeremy.bennett at embecosm dot com Created attachment 7168 --> https://sourceware.org/bugzilla/attachment.cgi?id=7168&action=edit Patch to update user manual for this issue. The GDB manual (section 5.1.2, "Setting Watchpoints") states: "If gdb cannot set a hardware watchpoint, it sets a software watchpoint,..." This appears to only be true for native targets. On a remote target connecting over Remote Serial Protocol, GDB will just report that hardware breakpoints are not supported. Could not insert hardware breakpoints: You may have requested too many hardware breakpoints/watchpoints The user must explicitly request software watchpoints using set can-use-hw-watchpoints 0 Problem found using GDB for ARC. This really needs fixing in remote.c, but in the meantime, I attach a small patch to the documentation: 2013-05-13 Jeremy Bennett <jeremy.bennett@embecosm.com> * doc/gdb.texinfo (Setting Watchpoints): Note that automatic fallback to software watchpoints does not happen with remote targets. -- You are receiving this mail because: You are on the CC list for the bug.
next reply other threads:[~2013-08-27 17:04 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-08-27 17:04 jeremy.bennett at embecosm dot com [this message] 2013-08-27 19:05 ` [Bug breakpoints/15902] " akolesov at synopsys dot com 2013-08-27 20:03 ` akolesov at synopsys 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-15902-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).