From: "M.M. Kettenis" <m.m.kettenis@alumnus.utwente.nl>
To: Daniel Jacobowitz <drow@false.org>, gdb-patches@sources.redhat.com
Subject: Re: gdb and gdbserver support for MIPS NPTL
Date: Thu, 17 Mar 2005 16:06:00 -0000 [thread overview]
Message-ID: <7320225758197692@weblx058.utsp.utwente.nl> (raw)
In-Reply-To: <20050317152208.GA31661@nevyn.them.org>
Daniel Jacobowitz <drow@false.org> wrote:
> This patch provides ps_get_thread_area for both mips-linux-gdb and
> mips-linux gdbserver. I haven't checked it in yet, because the
> corresponding kernel changes and glibc changes are still pending; I'll check
> it in when they've been approved. Just wanted to get it off my hard drive.
The code include <linux/elf.h> that should be avoided if possible.
Is it still possible to change your glibc patches such that you can
avoid it?
> Index: gdb/gdb/gdbserver/linux-mips-low.c
> ===================================================================
> --- gdb.orig/gdb/gdbserver/linux-mips-low.c 2002-06-11 13:32:39.000000000 -0400
> +++ gdb/gdb/gdbserver/linux-mips-low.c 2005-02-13 21:59:15.000000000 -0500
> @@ -22,6 +22,26 @@
> #include "server.h"
> #include "linux-low.h"
>
> +#include <sys/ptrace.h>
> +
> +/* Correct for all GNU/Linux targets (for quite some time). */
> +#define GDB_GREGSET_T elf_gregset_t
> +#define GDB_FPREGSET_T elf_fpregset_t
> +
> +#ifndef HAVE_ELF_FPREGSET_T
> +/* Make sure we have said types. Not all platforms bring in <linux/elf.h>
> + via <sys/procfs.h>. */
> +#ifdef HAVE_LINUX_ELF_H
> +#include <linux/elf.h>
> +#endif
> +#endif
> +
next prev parent reply other threads:[~2005-03-17 16:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-17 15:23 Daniel Jacobowitz
2005-03-17 16:06 ` M.M. Kettenis [this message]
2005-03-17 16:12 ` 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=7320225758197692@weblx058.utsp.utwente.nl \
--to=m.m.kettenis@alumnus.utwente.nl \
--cc=drow@false.org \
--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