From: James Clarke <jrtc27@jrtc27.com>
To: gdb-patches@sourceware.org
Cc: James Clarke <jrtc27@jrtc27.com>
Subject: [PATCH v2 2/2] gdb: Add missing #ifdef USE_THREAD_DB to gdbserver
Date: Fri, 19 Jan 2018 17:23:00 -0000 [thread overview]
Message-ID: <20180119172250.91520-2-jrtc27@jrtc27.com> (raw)
In-Reply-To: <20180119172250.91520-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, otherwise
linking fails with "undefined reference to
`thread_db_notice_clone(thread_info*, ptid_t)'" on architectures
without thread_db.
---
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.8.5.3
next prev parent reply other threads:[~2018-01-19 17:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-19 17:23 [PATCH v2 1/2] gdb: Fix ia64 defining TRAP_HWBKPT before including gdb_wait.h James Clarke
2018-01-19 17:23 ` James Clarke [this message]
2018-01-19 18:39 ` [PATCH v2 2/2] gdb: Add missing #ifdef USE_THREAD_DB to gdbserver Pedro Alves
2018-01-19 22:35 ` James Clarke
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=20180119172250.91520-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