From: Daniel Jacobowitz <drow@false.org>
To: "David S. Miller" <davem@davemloft.net>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [PATCH]: Fix thread debugging on Sparc/Linux
Date: Tue, 04 Apr 2006 22:06:00 -0000 [thread overview]
Message-ID: <20060404220648.GA11871@nevyn.them.org> (raw)
In-Reply-To: <20060404.145455.31557955.davem@davemloft.net>
On Tue, Apr 04, 2006 at 02:54:55PM -0700, David S. Miller wrote:
> From: "David S. Miller" <davem@davemloft.net>
> Date: Sat, 01 Apr 2006 23:12:03 -0800 (PST)
>
> > Normally the {supply,fill}_{gregset,fpregset}() functions don't
> > get used on Sparc/Linux because all of the register stuff does
> > ptrace() inside of sparc-nat.c
> >
> > However, for proc-service.c thread debugging (and I think also
> > for core files) these routines do get used.
Yes, it looks like they will currently be used for core regsets on
SPARC. They shouldn't be; the Linux port could use an update to the
new regset mechanism, used by e.g. the BSDs. That could add
cross-debug support for core files also.
They are also used for thread debugging, but that's general
GDB-for-Linux lameness; that part of linux-thread-db.c needs to be
eliminated. It's on the todo list.
> > Currently, we're linking in sparc-sol2-nat.o but that doesn't
> > work so well because it hardcodes using the sparc_sol2_gregset
> > which causes no end of troubles if used on another native Sparc
> > platform.
> >
> > Any objections to the following fix?
>
> Since there were no objections, I've checked in the fix.
Thanks. But, in the future, could you please wait for your patches to
be reviewed like everyone else (or ask to be the maintainer for this
port)?
You added includes to source files, so Makefile.in needs to be updated.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2006-04-04 22:06 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-02 7:12 David S. Miller
2006-04-04 21:54 ` David S. Miller
2006-04-04 22:06 ` Daniel Jacobowitz [this message]
2006-04-04 22:08 ` David S. Miller
2006-04-04 22:14 ` Daniel Jacobowitz
2006-04-04 22:22 ` David S. Miller
2006-04-04 22:43 ` Daniel Jacobowitz
2006-04-04 22:54 ` David S. Miller
2006-04-04 23:11 ` Daniel Jacobowitz
2006-04-04 23:12 ` David S. Miller
2006-04-04 23:52 ` David S. Miller
2006-04-04 23:58 ` Michael Snyder
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=20060404220648.GA11871@nevyn.them.org \
--to=drow@false.org \
--cc=davem@davemloft.net \
--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