From: "David S. Miller" <davem@davemloft.net>
To: drow@false.org
Cc: gdb-patches@sources.redhat.com
Subject: Re: [PATCH]: Fix thread debugging on Sparc/Linux
Date: Tue, 04 Apr 2006 22:54:00 -0000 [thread overview]
Message-ID: <20060404.155456.38752686.davem@davemloft.net> (raw)
In-Reply-To: <20060404224341.GA13358@nevyn.them.org>
From: Daniel Jacobowitz <drow@false.org>
Date: Tue, 4 Apr 2006 18:43:41 -0400
> In that case, I can save you one bit of debugging: a lot of thread
> tests are broken on SPARC, because linux_nat_thread_alive (or something
> with a similar name) tries to use PTRACE_PEEKUSR to test whether a
> thread is alive, but the SPARC ptrace interface doesn't implement that,
> only PTRACE_GETREGS.
I'm two shoelaces ahead of you.
I'm adding support for PTRACE_PEEKUSER with offset 0 in the kernel in
order to cure this. Linux/Sparc is the only platform that doesn't
support this and just returning a dummy zero value for this special
case is fine with me.
There are many more much deeper issues once you get past this, which
I plan to get to. I need reliable Linux thread debugging in gdb in
order to work on Mono.
The checkpoint/restart stuff is also non-functional on Linux/Sparc,
but I think that could be due to some bug in event message handling on
that platform.
next prev parent reply other threads:[~2006-04-04 22:54 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
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 [this message]
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=20060404.155456.38752686.davem@davemloft.net \
--to=davem@davemloft.net \
--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