From: Pedro Alves <palves@redhat.com>
To: James Clarke <jrtc27@jrtc27.com>, gdb-patches@sourceware.org
Subject: Re: [PATCH v2 2/2] gdb: Add missing #ifdef USE_THREAD_DB to gdbserver
Date: Fri, 19 Jan 2018 18:39:00 -0000 [thread overview]
Message-ID: <63cbe53a-de3d-4413-b79b-ef6b34a951aa@redhat.com> (raw)
In-Reply-To: <20180119172250.91520-2-jrtc27@jrtc27.com>
On 01/19/2018 05:22 PM, James Clarke wrote:
> 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.
Note, we put the "why" info on the git commit log, not in the ChangeLog.
Also, gdb/ChangeLog -> gdb/gdbserver/ChangeLog.
I've amended those nits and pushed both patches in.
AFAICT, you have a copyright assignment on file for other projects,
but not for GDB. The patches are small enough for that to not be
an issue, but if you're planning on contributing more, it'll be
good to take care of that.
Thanks!
Pedro Alves
From a0aad53764f45a634462288befe4c2eaecbf302d Mon Sep 17 00:00:00 2001
From: James Clarke <jrtc27@jrtc27.com>
Date: Fri, 19 Jan 2018 17:22:50 +0000
Subject: [PATCH] gdb: Add missing #ifdef USE_THREAD_DB to gdbserver
Otherwise, linking fails with:
[...]/linux-low.c:664: undefined reference to `thread_db_notice_clone(thread_info*, ptid_t)'
gdb/gdbserver/ChangeLog:
* linux-low.c (handle_extended_wait): Surround call to
thread_db_notice_clone with #ifdef USE_THREAD_DB.
---
gdb/gdbserver/ChangeLog | 5 +++++
gdb/gdbserver/linux-low.c | 2 ++
2 files changed, 7 insertions(+)
diff --git a/gdb/gdbserver/ChangeLog b/gdb/gdbserver/ChangeLog
index f1836559539..877b6e6226a 100644
--- a/gdb/gdbserver/ChangeLog
+++ b/gdb/gdbserver/ChangeLog
@@ -1,3 +1,8 @@
+2018-01-19 James Clarke <jrtc27@jrtc27.com>
+
+ * linux-low.c (handle_extended_wait): Surround call to
+ thread_db_notice_clone with #ifdef USE_THREAD_DB.
+
2018-01-17 Simon Marchi <simon.marchi@ericsson.com>
* linux-low.c (attach_proc_task_lwp_callback): Adjust to
diff --git a/gdb/gdbserver/linux-low.c b/gdb/gdbserver/linux-low.c
index 8117fc6ca8b..38142bba03d 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;
--
2.14.3
next prev parent reply other threads:[~2018-01-19 18:39 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 ` [PATCH v2 2/2] gdb: Add missing #ifdef USE_THREAD_DB to gdbserver James Clarke
2018-01-19 18:39 ` Pedro Alves [this message]
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=63cbe53a-de3d-4413-b79b-ef6b34a951aa@redhat.com \
--to=palves@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=jrtc27@jrtc27.com \
/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