From: Steffen Malmgaard Mortensen <smm@futarque.com>
To: linux-mips@linux-mips.org
Subject: Re: Problem debugging multi-threaded app
Date: Wed, 29 Sep 2004 08:14:50 +0200 [thread overview]
Message-ID: <1096438490.5227.24.camel@localhost> (raw)
In-Reply-To: <1096362700.5227.19.camel@localhost>
[-- Attachment #1: Type: text/plain, Size: 1065 bytes --]
Hi again,
Sorry - I know I shouldn't even be allowed to ask questions...... It was
another old, known bug - I was running with stripped libpthread......
/Steffen
On Tue, 2004-09-28 at 11:11, Steffen Malmgaard Mortensen wrote:
> 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
>
>
>
[-- Attachment #2: Type: text/html, Size: 1455 bytes --]
prev parent reply other threads:[~2004-09-29 6:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-28 9:11 Problem debugging multi-threaded app Steffen Malmgaard Mortensen
2004-09-29 6:14 ` Steffen Malmgaard Mortensen [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=1096438490.5227.24.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 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.