From: Stuart Hughes <seh@zee2.com>
To: Daniel Jacobowitz <dan@debian.org>
Cc: Linux-MIPS <linux-mips@linux-mips.org>
Subject: Re: cannot debug multi-threaded programs with gdb
Date: Fri, 13 Sep 2002 15:10:32 +0100 [thread overview]
Message-ID: <3D81F1D8.5E92F8EB@zee2.com> (raw)
In-Reply-To: 20020913135113.GA10721@nevyn.them.org
[-- Attachment #1: Type: text/plain, Size: 1457 bytes --]
Hi Daniel,
Thanks for your help. I also just found a posting by you from January
explaining this. I tried it out, and it works like a dream. FWIW I've
attached a patch I applied to glibc.
Regards, Stuart
Daniel Jacobowitz wrote:
>
> On Fri, Sep 13, 2002 at 11:07:15AM +0100, Stuart Hughes wrote:
> > Hi,
> >
> > I've been trying to debug a simple multi-threaded test program using
> > gdb, and it always fails as follows:
> >
> > [New Thread 1024 (LWP
> > 39)]
> >
> > Program received signal SIGTRAP, Trace/breakpoint
> > trap.
> > [Switching to Thread 1024 (LWP
> > 39)]
> > warning: Warning: GDB can't find the start of the function at
> > 0xffffffff.
> >
> > I've tried various different compilers, gdb, glibc version but the
> > problem is the same. Note that I can debug non-threaded c/c++ programs
> > without any problem. My environment is as follows:
> >
> > CPU: NEC VR5432
> > kernel: linux-2.4.10 + patches
> > glibc: 2.2.3 + patches
>
> Not enough patches I'd bet. Glibc 2.2.3 had an incorrect size listed
> for elf_gregset_t, and it was fixed in 2.2.5. That would cause this
> problem.
>
> > gdb: 5.2/3 from CVS
> > gcc: 3.1 (also tried 3.0.1)
> > binutils: Version 2.11.90.0.25
> >
> > Does anyone have any idea what is wrong and how to fix it.
> >
> > Regards, Stuart
> >
> >
>
> --
> Daniel Jacobowitz
> MontaVista Software Debian GNU/Linux Developer
[-- Attachment #2: glibc-2.2.3-gdb-pthread-diff --]
[-- Type: text/plain, Size: 518 bytes --]
--- glibc-2.2.3/sysdeps/unix/sysv/linux/mips/sys/procfs.h.orig Fri Sep 13 14:26:42 2002
+++ glibc-2.2.3/sysdeps/unix/sysv/linux/mips/sys/procfs.h Fri Sep 13 14:26:54 2002
@@ -101,8 +101,8 @@
typedef void *psaddr_t;
/* Register sets. Linux has different names. */
-typedef gregset_t prgregset_t;
-typedef fpregset_t prfpregset_t;
+typedef elf_gregset_t prgregset_t;
+typedef elf_fpregset_t prfpregset_t;
/* We don't have any differences between processes and threads,
therefore habe only ine PID type. */
prev parent reply other threads:[~2002-09-13 14:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-13 10:07 cannot debug multi-threaded programs with gdb Stuart Hughes
2002-09-13 13:51 ` Daniel Jacobowitz
2002-09-13 14:10 ` Stuart Hughes [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=3D81F1D8.5E92F8EB@zee2.com \
--to=seh@zee2.com \
--cc=dan@debian.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox