From: Daniel Jacobowitz <drow@false.org>
To: Tobias Erbsland <terbsland@printsoft.ch>
Cc: gdb@sources.redhat.com
Subject: Re: Threading bug, already solved, or is there a workaround?
Date: Wed, 01 Dec 2004 17:16:00 -0000 [thread overview]
Message-ID: <20041201171640.GA8619@nevyn.them.org> (raw)
In-Reply-To: <200412011252.47465.terbsland@printsoft.ch>
On Wed, Dec 01, 2004 at 12:52:47PM +0100, Tobias Erbsland wrote:
>
> Hello
>
> I'm currently try to debug a multithreaded application with gdb. It seems that
> there are this threading problems described in the PROBLEMS document.
> (It's a SuSE 9.2, but i installed gdb 6.3 in the hope, the bug is already
> solved.)
>
> Is there already a solution for that problem? Or is there a workaround?
Which problem, specifically, do you mean? What symptoms do you see?
--
Daniel Jacobowitz
next prev parent reply other threads:[~2004-12-01 17:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-01 11:53 Tobias Erbsland
2004-12-01 17:16 ` Daniel Jacobowitz [this message]
2004-12-02 9:56 ` Tobias Erbsland
2004-12-06 15:59 ` Daniel Jacobowitz
2004-12-06 16:16 ` Duncan Sands
2004-12-08 9:07 ` Tobias Erbsland
2004-12-06 15:45 Markus Riese
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=20041201171640.GA8619@nevyn.them.org \
--to=drow@false.org \
--cc=gdb@sources.redhat.com \
--cc=terbsland@printsoft.ch \
/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