Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: Daniel THOMPSON <daniel.thompson@st.com>
Cc: Claudia Salzberg <salzberg@us.ibm.com>, gdb@sources.redhat.com
Subject: Re: unable to debug remotely with threads on ppc target with gdb6.1/6.3
Date: Tue, 12 Apr 2005 12:06:00 -0000	[thread overview]
Message-ID: <20050412120620.GA6951@nevyn.them.org> (raw)
In-Reply-To: <425B7E46.8040408@st.com>

On Tue, Apr 12, 2005 at 08:52:38AM +0100, Daniel THOMPSON wrote:
> Claudia Salzberg wrote:
> >I have tried both gdb 6.1 the latest version (6.3) and am trying to debug 
> >a simple threaded program using pthreads remotely.   The target board is a 
> >440GP and the host is an x86 box.  I see references to similar problems in 
> >past posts from 12 2004 (
> >http://sourceware.org/ml/gdb/2004-12/msg00028.html) but did not see if a 
> >patch was created.
> 
> No I am not aware of any patch fixing this issue.
> 
> The problem (as the thread says) is that ps_lgetregs is not implemented 
> inside the gdbserver on PPC (or any other machine that uses 
> PEEKUSER/POKEUSER to access its register sets).
> 
> You should be able to jury rig a version by copying the code in 
> ppc-linux-nat.c:fill_gregset() into the ps_lgetregs function and 
> modifying the code to target the gdbserver register cache rather then 
> the gdb register cache.
> 
> There is, of course, a proper to way to do the above but you might want 
> to confirm the above works first ;-)

That's not Claudia's problem; the above only applies to NPTL, and she
appears to be using LinuxThreads from the error logs.

-- 
Daniel Jacobowitz
CodeSourcery, LLC


  reply	other threads:[~2005-04-12 12:06 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-11 16:29 Claudia Salzberg
2005-04-11 16:37 ` Daniel Jacobowitz
2005-04-12  7:52 ` Daniel THOMPSON
2005-04-12 12:06   ` Daniel Jacobowitz [this message]
2005-04-12 16:35     ` Claudia Salzberg

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=20050412120620.GA6951@nevyn.them.org \
    --to=drow@false.org \
    --cc=daniel.thompson@st.com \
    --cc=gdb@sources.redhat.com \
    --cc=salzberg@us.ibm.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