public inbox for gdb-cvs@sourceware.org
help / color / mirror / Atom feed
From: John Baldwin <jhb@sourceware.org>
To: gdb-cvs@sourceware.org
Subject: [binutils-gdb] aarch64-fbsd-nat: Move definition of debug_regs_probed under HAVE_DBREG.
Date: Thu, 26 May 2022 21:15:46 +0000 (GMT)	[thread overview]
Message-ID: <20220526211546.114A738344E5@sourceware.org> (raw)

https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=b2fdd31b03ef01a9a790ecb5d0dc0fea209b49ec

commit b2fdd31b03ef01a9a790ecb5d0dc0fea209b49ec
Author: John Baldwin <jhb@FreeBSD.org>
Date:   Thu May 26 14:14:46 2022 -0700

    aarch64-fbsd-nat: Move definition of debug_regs_probed under HAVE_DBREG.
    
    This fixes the build on older FreeBSD systems without support for
    hardware breakpoints/watchpoints.

Diff:
---
 gdb/aarch64-fbsd-nat.c | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/gdb/aarch64-fbsd-nat.c b/gdb/aarch64-fbsd-nat.c
index fb7a29b5afb..d8cf6227e73 100644
--- a/gdb/aarch64-fbsd-nat.c
+++ b/gdb/aarch64-fbsd-nat.c
@@ -76,7 +76,6 @@ private:
 };
 
 static aarch64_fbsd_nat_target the_aarch64_fbsd_nat_target;
-bool aarch64_fbsd_nat_target::debug_regs_probed;
 
 /* Fetch register REGNUM from the inferior.  If REGNUM is -1, do this
    for all registers.  */
@@ -155,6 +154,8 @@ aarch64_fbsd_nat_target::read_description ()
 }
 
 #ifdef HAVE_DBREG
+bool aarch64_fbsd_nat_target::debug_regs_probed;
+
 /* Set of threads which need to update debug registers on next resume.  */
 
 static std::unordered_set<lwpid_t> aarch64_debug_pending_threads;


                 reply	other threads:[~2022-05-26 21:15 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20220526211546.114A738344E5@sourceware.org \
    --to=jhb@sourceware.org \
    --cc=gdb-cvs@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: link
Be 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).