Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@mvista.com>
To: nak26 <nak26@drexel.edu>
Cc: gdb@sources.redhat.com
Subject: Re: gdbserver multithreaded debugging problem
Date: Mon, 23 Jun 2003 19:49:00 -0000	[thread overview]
Message-ID: <20030623194935.GA11083@nevyn.them.org> (raw)
In-Reply-To: <3EF77554@webmail.drexel.edu>

On Mon, Jun 23, 2003 at 03:39:06PM -0400, nak26 wrote:
> Hi:
> 
> I am trying to use gdbserver to remotely debug a multithreaded application.
> 
> Remote host is a IA32, running MontaVista Linux 3.0 kernel v 2.4.18; gdbserver 
> from the 5.3 release tarball, patched with the PREPARE_TO_PROCEED patch, and 
> built on the remote host.
> 
> Local host is an IA32 machine, running RedHat 8.0, gdb v 5.2.1-4.
> 
> I get a "Real-time event 32"-signal as each thread is spun up, execution 
> stops, and I have to re-continue. After all the threads are created and I hit 
> a breakpoint, info thread only displays the main thread.
> 
> I don't see this problem while debugging with gdb (5.2.1) on the remote (and 
> the local) target
> .
> Is there anything I can do to solve the problem I am experiencing with 
> gdbserver?

Did gdbserver detect thread support when you built it?  Check the output
of configure.

-- 
Daniel Jacobowitz
MontaVista Software                         Debian GNU/Linux Developer


  parent reply	other threads:[~2003-06-23 19:49 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-23 19:39 nak26
2003-06-23 19:45 ` Cal Erickson
2003-06-23 19:49 ` Daniel Jacobowitz [this message]
2003-06-24 14:54 nak26

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=20030623194935.GA11083@nevyn.them.org \
    --to=drow@mvista.com \
    --cc=gdb@sources.redhat.com \
    --cc=nak26@drexel.edu \
    /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