Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
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 23:11:00 -0000	[thread overview]
Message-ID: <20060404231102.GA14012@nevyn.them.org> (raw)
In-Reply-To: <20060404.155456.38752686.davem@davemloft.net>

On Tue, Apr 04, 2006 at 03:54:56PM -0700, David S. Miller wrote:
> 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.

OK, that works too :-)

> 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.

Is gdb a 32-bit or 64-bit binary?  I bet there's problems with a
32-bit binary.  At least one is that the event message is
stored as a long.

Hmm, might want a compat_ptrace_request.

-- 
Daniel Jacobowitz
CodeSourcery


  reply	other threads:[~2006-04-04 23:11 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
2006-04-04 23:11               ` Daniel Jacobowitz [this message]
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=20060404231102.GA14012@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