From: Daniel Jacobowitz <drow@mvista.com>
To: Andrew Cagney <ac131313@cygnus.com>
Cc: Michael Snyder <msnyder@redhat.com>, gdb-patches@sources.redhat.com
Subject: Re: [RFA] Save SSE registers to generated core files, without breaking other architectures
Date: Sun, 14 Apr 2002 18:51:00 -0000 [thread overview]
Message-ID: <20020414215208.B25085@nevyn.them.org> (raw)
In-Reply-To: <3CBA0115.70009@cygnus.com>
On Sun, Apr 14, 2002 at 06:22:13PM -0400, Andrew Cagney wrote:
> >Daniel Jacobowitz wrote:
> >
> >>
> >>How does this patch look? The original problem was that we can not rely
> >>on
> >>HAVE_PTRACE_FPXREGSET, because the presence of PTRACE_FPXREGSET doesn't
> >>imply that GDB has a fill_fpxregset function available. I updated it to
> >>check for a separate flag. It's not ideal, but until we separate regset
> >>handling into an appropriate vector, it's the best we can do (I think).
> >>
> >>OK?
> >
> >
> >Well, I like it (and thanks for working on it),
> >but Andrew might have something to say about adding
> >a new macro. Andrew?
>
>
> >>* config/i386/tm-linux.h: Define FILL_FPXREGSET.
>
> linux-proc.c is only built native so I think FILL_.. should only be
> defined for native builds => config/i386/nm-linux.h.
>
> Having #ifdef code enabled via a tm.h file macro just feels wrong.
And the function in question is even in i386-linux-nat.c. nm-linux.h
sounds like the right place to put it. OK with that change, then?
--
Daniel Jacobowitz Carnegie Mellon University
MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2002-04-15 1:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-02 11:55 Daniel Jacobowitz
2002-04-02 14:00 ` Michael Snyder
2002-04-14 15:22 ` Andrew Cagney
2002-04-14 18:51 ` Daniel Jacobowitz [this message]
2002-04-14 19:09 ` Andrew Cagney
2002-04-24 14:47 ` [RFA] Save SSE registers to generated core files, without breakingother architectures Michael Snyder
2002-04-24 15:10 ` 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=20020414215208.B25085@nevyn.them.org \
--to=drow@mvista.com \
--cc=ac131313@cygnus.com \
--cc=gdb-patches@sources.redhat.com \
--cc=msnyder@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