public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: James Clarke <jrtc27@jrtc27.com>
To: gdb-patches@sourceware.org
Cc: James Clarke <jrtc27@jrtc27.com>
Subject: [PATCH 2/2] gdb: Add missing #ifdef USE_THREAD_DB to gdbserver
Date: Fri, 15 Dec 2017 00:04:00 -0000	[thread overview]
Message-ID: <20171215000434.47315-2-jrtc27@jrtc27.com> (raw)
In-Reply-To: <20171215000434.47315-1-jrtc27@jrtc27.com>

gdb/ChangeLog:
	* gdbserver/linux-low.c (handle_extended_wait): Surround call to
	thread_db_notice_clone with #ifdef USE_THREAD_DB.
---
[Originally erroneously sent to the binutils mailing list]

 gdb/gdbserver/linux-low.c |    2 ++
 1 file changed, 2 insertions(+)

diff --git a/gdb/gdbserver/linux-low.c b/gdb/gdbserver/linux-low.c
index f6a52d5..398cd70 100644
--- a/gdb/gdbserver/linux-low.c
+++ b/gdb/gdbserver/linux-low.c
@@ -661,7 +661,9 @@ handle_extended_wait (struct lwp_info **orig_event_lwp, int wstat)
 	  new_lwp->status_pending = status;
 	}

+#ifdef USE_THREAD_DB
       thread_db_notice_clone (event_thr, ptid);
+#endif

       /* Don't report the event.  */
       return 1;
--
1.7.10.4

  reply	other threads:[~2017-12-15  0:04 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-15  0:04 [PATCH 1/2] gdb: Fix ia64 defining TRAP_HWBKPT before including gdb_wait.h James Clarke
2017-12-15  0:04 ` James Clarke [this message]
2018-01-19 16:48   ` [PATCH 2/2] gdb: Add missing #ifdef USE_THREAD_DB to gdbserver Pedro Alves
2018-01-19 16:55     ` James Clarke
2018-01-19 16:57       ` Pedro Alves
2018-01-19 17:01         ` James Clarke
2018-01-19 16:34 ` [PATCH 1/2] gdb: Fix ia64 defining TRAP_HWBKPT before including gdb_wait.h James Clarke
2018-01-19 16:43 ` Pedro Alves

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=20171215000434.47315-2-jrtc27@jrtc27.com \
    --to=jrtc27@jrtc27.com \
    --cc=gdb-patches@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).