From: Steffen Malmgaard Mortensen <smm@futarque.com>
To: linux-mips@linux-mips.org
Subject: Problem debugging multi-threaded app
Date: Tue, 28 Sep 2004 11:11:40 +0200 [thread overview]
Message-ID: <1096362700.5227.19.camel@localhost> (raw)
Hi all,
I'm trying to debug a multi-threaded app using gdbserver/gdb. I see the
same problems as described in
http://www.linux-mips.org/archives/linux-mips/2002-09/msg00155.html -
the program receives SIG32, but gdb doesn't associate that with thread
creation. The solution back in 2002 was to upgrade the tool-chain, but
I'm not sure what versions I should use today (and what patches). I'm
currently using:
CPU: Ati X225 (mips4kc - little endian)
kernel: linux 2.4.18 + vendor patches
glibc: 2.3.2
gcc: 3.3.2
binutils: 2.14
(the three above from crosstool 0.27)
gdb/gdbserver: 6.2
According to strace gdbserver loads libthread_db as it should, but gdb
on my host doesn't load libthread_db.
Any help/suggestions will be greatly appriciated...
Best regards,
Steffen
next reply other threads:[~2004-09-28 9:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-28 9:11 Steffen Malmgaard Mortensen [this message]
2004-09-29 6:14 ` Problem debugging multi-threaded app Steffen Malmgaard Mortensen
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=1096362700.5227.19.camel@localhost \
--to=smm@futarque.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox