Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@mvista.com>
To: Frank.Christ@RSBICK.rohde-schwarz.com
Cc: gdb@sources.redhat.com
Subject: Re: Remote Debugging Of Multithreaded Application on PPC 82xx
Date: Fri, 14 Mar 2003 14:17:00 -0000	[thread overview]
Message-ID: <20030314141737.GA9144@nevyn.them.org> (raw)
In-Reply-To: <C1256CE9.004CEAE2.00@mail.rohde-schwarz.com>

On Fri, Mar 14, 2003 at 03:03:25PM +0100, Frank.Christ@RSBICK.rohde-schwarz.com wrote:
> I am trying to setup a remote debugging session, so that I can debug my
> multithreaded
> application running on PPC 82xx and use gdb on my Intel host (i686, SuSE 7.0).
> 
> I downloaded gdb version 5.3 and compiled gdb on the host (with target
> powerpc-linux).
> I also cross-compiled gdbserver (with option powerpc-linux).
> 
> I have /lib/libthread_db.so.1 on the 8xx
>   have the target filesystem layout available on the host
>   have solib-absolute-prefix set to point to the target libraries
> (solib-absolute-prefix=/opt/elinos/cdk/ppc/82xx/libc6/powerpc-linux)
> 
> I can start the gdbserver on the target and gdb on the host and have a
> connection by tcp/ip.
> The application is multithreaded and uses the libpthread library. I can put
> breakpoints in
> every thread and break into my code. "info threads" gives all my threads and
> everything
> seems fine.
> 
> However:
> I can step through the main thread, but I cannot step through all my other
> threads. When
> I try to step with next in a client thread I get the following message:
> 
> -------------------------------------
>  (gdb) next
> 
> Program received signal SIGTRAP, Trace/breakpoint trap.
> [Switching to Thread 1024]
> 0x0feee8a4 in nanosleep () from
> /opt/elinos/cdk/ppc/82xx/libc6/powerpc-linux/lib/libc.so.6
> ------------------------------------
> 
> Any hints what my be wrong with my configuration?

You may want to try the PREPARE_TO_PROCEED patch which I posted to
gdb-patches yesterday; you can find the list archives on
http://sources.redhat.com/ml/gdb-patches/2003-03/.

There are also some bugs related to stepping alternate threads that
require a change to the remote protocol, but I didn't get a consensus
on how to solve them yet (and I ran out of time to pursue it; I'll try
again soon).

-- 
Daniel Jacobowitz
MontaVista Software                         Debian GNU/Linux Developer


      reply	other threads:[~2003-03-14 14:17 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-14 14:03 Frank.Christ
2003-03-14 14:17 ` Daniel Jacobowitz [this message]

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=20030314141737.GA9144@nevyn.them.org \
    --to=drow@mvista.com \
    --cc=Frank.Christ@RSBICK.rohde-schwarz.com \
    --cc=gdb@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