All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stuart Hughes <seh@zee2.com>
To: Linux-MIPS <linux-mips@linux-mips.org>
Subject: cannot debug multi-threaded programs with gdb/gdbserver
Date: Tue, 17 Sep 2002 18:03:15 +0100	[thread overview]
Message-ID: <3D876053.C2CD1D8C@zee2.com> (raw)

Hi,

I managed to get gdb to do multi-threaded debug using a gdb on the
target, after Daniel J helped with a patch to sys/procfs.h

I am now trying to do host target with gdb/gdbserver.  The program on
the target uses pthreads.

I can connect, but as soon as you try to continue (to a breakpoint) I
get:

Program received signal SIG32, Real-time event 32.
warning: Warning: GDB can't find the start of the function at
0x2abee684.
....

I know that SIG32 is used for the thread control on the target, but I'm
not sure if the host gdb is supposed to receive this.  I tried "set
handle SIG32 pass noprint nostop"
and variations, but this didn't help.
 
Does anyone know whether there is some special setup needed on
gdb/gdbserver to use the multi-threaded gdbserver ??



My environment is as follows:

CPU:		NEC VR5432
kernel: 	linux-2.4.18 + patches
glibc:		2.2.3 + patches
gdb:		5.2/3 from CVS
gcc:		3.1
binutils:	Version 2.11.90.0.25


cross-gdb configured using: 

configure --prefix=/usr --target=mipsel-linux --disable-sim
--disable-tcl --enable-threads --enable-shared

gdbserver configured using:

configure --prefix=/usr --host=mipsel-linux --target=mipsel-linux
--enable-threads --enable-shared


Regards, Stuart

             reply	other threads:[~2002-09-17 17:03 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-17 17:03 Stuart Hughes [this message]
2002-09-17 17:24 ` cannot debug multi-threaded programs with gdb/gdbserver Steven J. Hill
2002-09-17 18:25   ` Daniel Jacobowitz
2002-09-17 19:46     ` Steven J. Hill
2002-09-17 20:47       ` Daniel Jacobowitz
2002-09-18  7:48     ` Stuart Hughes
2002-09-18 12:10   ` Johannes Stezenbach
2002-09-18 13:23     ` Daniel Jacobowitz

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=3D876053.C2CD1D8C@zee2.com \
    --to=seh@zee2.com \
    --cc=linux-mips@linux-mips.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.