From: Pedro Alves <palves@redhat.com>
To: gdb-patches@sourceware.org
Subject: [PATCH 6/6] Only define 'struct lwp_info'::thread_known if using libthread-db.
Date: Wed, 17 Apr 2013 02:54:00 -0000 [thread overview]
Message-ID: <20130416183125.540.35758.stgit@brno.lan> (raw)
In-Reply-To: <20130416183043.540.32214.stgit@brno.lan>
A small cleanup. 'struct lwp_info'::thread_known is only useful for
thread-db.c.
gdbserver/
2013-04-16 Pedro Alves <palves@redhat.com>
* linux-low.h (struct lwp_info) <thread_known>: Move under
the USE_THREAD_DB #ifdef.
---
gdb/gdbserver/linux-low.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/gdb/gdbserver/linux-low.h b/gdb/gdbserver/linux-low.h
index 834dd91..205d803 100644
--- a/gdb/gdbserver/linux-low.h
+++ b/gdb/gdbserver/linux-low.h
@@ -267,8 +267,8 @@ struct lwp_info
stepping over later when it is resumed. */
int need_step_over;
- int thread_known;
#ifdef USE_THREAD_DB
+ int thread_known;
/* The thread handle, used for e.g. TLS access. Only valid if
THREAD_KNOWN is set. */
td_thrhandle_t th;
next prev parent reply other threads:[~2013-04-16 18:31 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-17 0:32 [PATCH 0/6] thread_db.h issues Pedro Alves
2013-04-17 0:55 ` [PATCH 1/6] PR build/11881: LIBTHREAD_DB_SO can be undefined Pedro Alves
2013-04-17 1:04 ` [PATCH 2/6] Move glibc's fallback thread_db.h to a separate file Pedro Alves
2013-04-17 1:58 ` [PATCH 3/6] Update glibc_thread_db.h from upstream Pedro Alves
2013-04-17 2:42 ` [PATCH 4/6] copyright.py: Don't update glibc_thread_db.h Pedro Alves
2013-04-17 2:54 ` Pedro Alves [this message]
2013-04-17 2:54 ` [PATCH 5/6] Fix remaining GDBserver issues with !HAVE_THREAD_DB_H Pedro Alves
2013-04-17 4:56 ` Tom Tromey
2013-04-17 15:54 ` Use AC_DEFINE for USE_THREAD_DB (was: Re: [PATCH 5/6] Fix remaining GDBserver issues with !HAVE_THREAD_DB_H.) 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=20130416183125.540.35758.stgit@brno.lan \
--to=palves@redhat.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