Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Joel Brobecker <brobecker@adacore.com>
To: gdb-patches@sourceware.org
Cc: Joel Brobecker <brobecker@adacore.com>
Subject: [PATCH 3/4] Add procfs_find_LDT_entry declaration (procfs.h).
Date: Thu, 20 Sep 2012 16:34:00 -0000	[thread overview]
Message-ID: <1348158841-2313-4-git-send-email-brobecker@adacore.com> (raw)
In-Reply-To: <1348158841-2313-1-git-send-email-brobecker@adacore.com>

Add a declaration for procfs_find_LDT_entry in order to prevent
a compiler warning about this function missing one. This also
helps making sure that declaration and definition remain consistent.

gdb/ChangeLog:

        * procfs.h (procfs_find_LDT_entry): Add declaration.
        * sol-thread.c (ps_lgetLDT): Delete local declaration of
        function procfs_find_LDT_entry.
---
 gdb/procfs.h     |    7 +++++++
 gdb/sol-thread.c |    1 -
 2 files changed, 7 insertions(+), 1 deletions(-)

diff --git a/gdb/procfs.h b/gdb/procfs.h
index 8293322..9dbf531 100644
--- a/gdb/procfs.h
+++ b/gdb/procfs.h
@@ -34,3 +34,10 @@ extern void procfs_use_watchpoints (struct target_ops *t);
    'live' procinfo.  */
 
 extern ptid_t procfs_first_available (void);
+
+#if (defined(__i386__) || defined(__x86_64__)) && defined (sun)
+struct ssd;
+
+extern struct ssd *procfs_find_LDT_entry (ptid_t);
+#endif
+
diff --git a/gdb/sol-thread.c b/gdb/sol-thread.c
index 3577b5a..cd37615 100644
--- a/gdb/sol-thread.c
+++ b/gdb/sol-thread.c
@@ -1108,7 +1108,6 @@ ps_lgetLDT (gdb_ps_prochandle_t ph, lwpid_t lwpid,
 	    struct ssd *pldt)
 {
   /* NOTE: only used on Solaris, therefore OK to refer to procfs.c.  */
-  extern struct ssd *procfs_find_LDT_entry (ptid_t);
   struct ssd *ret;
 
   /* FIXME: can't I get the process ID from the prochandle or
-- 
1.6.5.rc2


  reply	other threads:[~2012-09-20 16:34 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-20 16:34 Various build-related fixes for solaris Joel Brobecker
2012-09-20 16:34 ` Joel Brobecker [this message]
2012-09-22 14:22   ` [PATCH 3/4] Add procfs_find_LDT_entry declaration (procfs.h) Jan Kratochvil
2012-09-27 12:56   ` checked in: " Joel Brobecker
2012-09-20 16:34 ` [PATCH 1/4] Fix declaration of proc_find_memory_regions Joel Brobecker
2012-09-27 12:55   ` checked in: " Joel Brobecker
2012-09-20 16:34 ` [PATCH 2/4] Make procfs.c:proc_get_LDT_entry static Joel Brobecker
2012-09-27 12:55   ` checked in: " Joel Brobecker
2012-09-20 16:44 ` [PATCH 4/4] Delete unused functions in sol-thread.c Joel Brobecker
2012-09-20 17:31   ` Pedro Alves
2012-09-20 21:43     ` Joel Brobecker
2012-09-20 22:25       ` Joel Brobecker
2012-09-20 22:25         ` Joel Brobecker
2012-09-24 16:27           ` Pedro Alves
2012-09-24 16:37             ` Joel Brobecker
2012-09-27 13:02           ` checked in: New unit sparc-sol-thread.c extracted from sol-thread.c Joel Brobecker
2012-09-24 16:18       ` [PATCH 4/4] Delete unused functions in sol-thread.c Pedro Alves
2012-09-24 16:40         ` Joel Brobecker
2012-09-27 13:04         ` checked in: sol-thread.c: Remove commented-out code Joel Brobecker
2012-09-27 12:59       ` checked in: [PATCH 4/4] Delete unused functions in sol-thread.c Joel Brobecker

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=1348158841-2313-4-git-send-email-brobecker@adacore.com \
    --to=brobecker@adacore.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