From: Daniel Jacobowitz <dan@debian.org>
To: Stuart Hughes <seh@zee2.com>
Cc: Linux-MIPS <linux-mips@linux-mips.org>
Subject: Re: cannot debug multi-threaded programs with gdb
Date: Fri, 13 Sep 2002 09:51:13 -0400 [thread overview]
Message-ID: <20020913135113.GA10721@nevyn.them.org> (raw)
In-Reply-To: <3D81B8D3.1609CD69@zee2.com>
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
next prev parent reply other threads:[~2002-09-13 13:51 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 [this message]
2002-09-13 14:10 ` Stuart Hughes
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=20020913135113.GA10721@nevyn.them.org \
--to=dan@debian.org \
--cc=linux-mips@linux-mips.org \
--cc=seh@zee2.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 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.