Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: dje@google.com (Doug Evans)
To: gdb-patches@sourceware.org
Subject: [RFA] remove struct process_info.tid
Date: Mon, 08 Dec 2008 04:21:00 -0000	[thread overview]
Message-ID: <20081208042025.9F59D1C7A13@localhost> (raw)

Hi.  I can't find any place where process_info.tid is used.

Ok to check in?

2008-12-07  Doug Evans  <dje@google.com>

	* linux-low.h (struct process_info): Delete member tid, unused.
	* thread-db.c (find_one_thread): Update.
	(maybe_attach_thread): Update.

Index: linux-low.h
===================================================================
RCS file: /cvs/src/src/gdb/gdbserver/linux-low.h,v
retrieving revision 1.23
diff -u -p -u -p -r1.23 linux-low.h
--- linux-low.h	28 Feb 2008 05:54:09 -0000	1.23
+++ linux-low.h	8 Dec 2008 04:16:39 -0000
@@ -130,7 +130,6 @@ struct process_info
   struct thread_resume *resume;
 
   int thread_known;
-  unsigned long tid;
 #ifdef HAVE_THREAD_DB_H
   /* The thread handle, used for e.g. TLS access.  Only valid if
      THREAD_KNOWN is set.  */
Index: thread-db.c
===================================================================
RCS file: /cvs/src/src/gdb/gdbserver/thread-db.c,v
retrieving revision 1.15
diff -u -p -u -p -r1.15 thread-db.c
--- thread-db.c	1 Jan 2008 22:53:14 -0000	1.15
+++ thread-db.c	8 Dec 2008 04:16:39 -0000
@@ -280,7 +280,6 @@ find_one_thread (int lwpid)
     return 0;
 
   process->thread_known = 1;
-  process->tid = ti.ti_tid;
   process->th = th;
 
   return 1;
@@ -313,7 +312,6 @@ maybe_attach_thread (const td_thrhandle_
 
   process = inferior_target_data (inferior);
 
-  process->tid = ti_p->ti_tid;
   process->thread_known = 1;
   process->th = *th_p;
 


             reply	other threads:[~2008-12-08  4:21 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-08  4:21 Doug Evans [this message]
2008-12-08 14:19 ` Daniel Jacobowitz

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=20081208042025.9F59D1C7A13@localhost \
    --to=dje@google.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