Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Andrew Cagney <ac131313@redhat.com>
To: gdb-patches@sources.redhat.com
Subject: [rfa:amd64] Fetch 32-bit thread area
Date: Fri, 27 Feb 2004 01:24:00 -0000	[thread overview]
Message-ID: <403E9C5F.2050803@redhat.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 155 bytes --]

Hello,

This modifies the amd64 code so that, when 32-bit, it fetches the 32-bit 
thread area register (I think this has been posted before?).

ok?
Andrew

[-- Attachment #2: diffs --]
[-- Type: text/plain, Size: 2901 bytes --]


        * amd64-linux-nat.c (ps_get_thread_area): When architecture is
	i386 use PTRACE_GET_THREAD_AREA.  Suggested by Roland McGrath.

Index: amd64-linux-nat.c
===================================================================
RCS file: /cvs/src/src/gdb/amd64-linux-nat.c,v
retrieving revision 1.1
diff -u -r1.1 amd64-linux-nat.c
--- amd64-linux-nat.c	25 Feb 2004 20:45:30 -0000	1.1
+++ amd64-linux-nat.c	27 Feb 2004 01:22:36 -0000
@@ -350,10 +350,14 @@
 }
 \f
 
+/* This function is called by libthread_db as part of its handling of
+   a request for a thread's local storage address.  */
+
 ps_err_e
 ps_get_thread_area (const struct ps_prochandle *ph,
                     lwpid_t lwpid, int idx, void **base)
 {
+#if 0
 /* This definition comes from prctl.h, but some kernels may not have it.  */
 #ifndef PTRACE_ARCH_PRCTL
 #define PTRACE_ARCH_PRCTL      30
@@ -377,6 +381,67 @@
       return PS_BADADDR;
     }
   return PS_ERR;               /* ptrace failed.  */
+#else
+  switch (TARGET_ARCHITECTURE->mach)
+    {
+    case bfd_mach_i386_i386:
+    case bfd_mach_i386_i386_intel_syntax:
+      {
+	/* The full structure is found in <asm-i386/ldt.h>.  The
+	   second integer is the LDT's base_address and that is used
+	   to locate the thread's local storage.  See i386-linux-nat.c
+	   more info.  */
+	unsigned int desc[4];
+
+	/* This code assumes that "int" is 32 bits and that
+           GET_THREAD_AREA returns no more than 4 int values.  */
+	gdb_assert (sizeof (int) == 4);	
+#ifndef PTRACE_GET_THREAD_AREA
+#define PTRACE_GET_THREAD_AREA 25
+#endif
+	if  (ptrace (PTRACE_GET_THREAD_AREA, 
+		     lwpid, (void *) (long) idx, (unsigned long) &desc) < 0)
+	  return PS_ERR;
+      
+	/* Extend the value to 64 bits.  Here it's assumed that a
+           "long" and a "void *" are the same.  */
+	(*base) = (void *) (long) desc[1];
+	return PS_OK;
+      }
+
+    case bfd_mach_x86_64:
+    case bfd_mach_x86_64_intel_syntax:
+
+      /* This definition comes from prctl.h, but some kernels may not
+         have it.  */
+#ifndef PTRACE_ARCH_PRCTL
+#define PTRACE_ARCH_PRCTL      30
+#endif
+      /* FIXME: ezannoni-2003-07-09 see comment above about include
+	 file order.  We could be getting bogus values for these two.  */
+      gdb_assert (FS < ELF_NGREG);
+      gdb_assert (GS < ELF_NGREG);
+      switch (idx)
+	{
+	case FS:
+	  if (ptrace (PTRACE_ARCH_PRCTL, lwpid, base, ARCH_GET_FS) == 0)
+	    return PS_OK;
+	  break;
+	case GS:
+	  if (ptrace (PTRACE_ARCH_PRCTL, lwpid, base, ARCH_GET_GS) == 0)
+	    return PS_OK;
+	  break;
+	default:                   /* Should not happen.  */
+	  return PS_BADADDR;
+	}
+      return PS_ERR;               /* ptrace failed.  */
+      
+    case bfd_mach_i386_i8086:
+      internal_error (__FILE__, __LINE__, "bad i8086 machine");
+    default:
+      internal_error (__FILE__, __LINE__, "bad_switch");
+    }
+#endif
 }
 \f
 

             reply	other threads:[~2004-02-27  1:24 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-27  1:24 Andrew Cagney [this message]
2004-02-28 11:51 ` Mark Kettenis
2004-02-28 15:22   ` Andrew Cagney
2004-02-28 17:37     ` Mark Kettenis
2004-02-28 19:40       ` Andrew Cagney

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=403E9C5F.2050803@redhat.com \
    --to=ac131313@redhat.com \
    --cc=gdb-patches@sources.redhat.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