Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Cal Erickson <cerickson@mvista.com>
To: nak26 <nak26@drexel.edu>
Cc: gdb@sources.redhat.com
Subject: Re: gdbserver multithreaded debugging problem
Date: Mon, 23 Jun 2003 19:45:00 -0000	[thread overview]
Message-ID: <3EF75754.3030202@mvista.com> (raw)
In-Reply-To: <3EF77554@webmail.drexel.edu>

Nik,
You are missing libthread_db.* in your LIBRAY PATH. If you had these
then you would not see the the SIG 32 messages.

Cal Erickson

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?
> 
> Here's gdb's output when debugging remotely:
> --------------------------------------------
> 
> (gdb) target remote 192.168.139.14:8888
> Remote debugging using 192.168.139.14:8888
> 0x40001390 in ?? ()
> (gdb) b osevent.cxx:215
> Breakpoint 1 at 0x826dd03: file ../../common/osevent.cxx, line 215.
> (gdb) cont
> Continuing.
> 
> Program received signal SIG32, Real-time event 32.
> 0x404b724d in ?? ()
> (gdb) c
> Continuing.
> 
> Program received signal SIG32, Real-time event 32.
> 0x404b724d in ?? ()
> (gdb)
> Continuing.
> 
> Program received signal SIG32, Real-time event 32.
> 0x404b724d in ?? ()
> (gdb)
> Continuing.
> 
> Program received signal SIG32, Real-time event 32.
> 0x404b724d in ?? ()
> (gdb)
> Continuing.
> 
> Program received signal SIG32, Real-time event 32.
> 0x404b724d in ?? ()
> (gdb)
> Continuing.
> 
> Program received signal SIG32, Real-time event 32.
> 0x404b724d in ?? ()
> (gdb)
> Continuing.
> 
> Program received signal SIG32, Real-time event 32.
> 0x404b724d in ?? ()
> (gdb)
> Continuing.
> 
> Breakpoint 1, OsEventManagerClass::eventLoop() (this=0x89caf78) at 
> ../../common/osevent.cxx:215
> 215           if (pTimer) {
> (gdb) info thread
>   1 Thread 3860  OsEventManagerClass::eventLoop() (this=0x89caf78) at 
> ../../common/osevent.cxx:215
> 
> ----------------------------------------------
> 
> Thanks,
> --Nik
> 
> 
> 


-- 
===========================================================================
Cal Erickson                 MontaVista Software Inc.
Linux Consultant             1237 E. Arques Ave.
Phone (408) 328-0304         Sunnyvale CA 94085
Fax   (408) 328-9204         web http://www.mvista.com
===========================================================================


  reply	other threads:[~2003-06-23 19:45 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 [this message]
2003-06-23 19:49 ` Daniel Jacobowitz
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=3EF75754.3030202@mvista.com \
    --to=cerickson@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