From: Daniel Jacobowitz <drow@false.org>
To: Jim Blandy <jimb@codesourcery.com>
Cc: gdb-patches@sourceware.org
Subject: Re: RFA: Make sigthread.exp more reliable
Date: Tue, 29 Jan 2008 18:14:00 -0000 [thread overview]
Message-ID: <20080129180922.GK3773@caradoc.them.org> (raw)
In-Reply-To: <m33at3vng0.fsf@codesourcery.com>
On Fri, Jan 11, 2008 at 05:31:59PM -0800, Jim Blandy wrote:
>
> sigthread.exp fails intermittently, because the program exits due to a
> segfault instead of the ^C GDB sends it. I believe this is because
> the threads throwing signals at each other don't wait until all the
> pthread_t variables are initialized before they do so. So they
> occasionally pass an uninitialized pthread_t to pthread_kill, which
> segfaults.
I'd been wondering what that crash was about...
> 2008-01-11 Jim Blandy <jimb@codesourcery.com>
>
> * gdb.threads/sigthread.c: Use barriers to ensure that
> child_thread and child_thread_two are always initialized before we
> start to use them.
Looks OK to me!
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2008-01-29 18:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-12 1:32 Jim Blandy
2008-01-29 18:14 ` Daniel Jacobowitz [this message]
2008-01-29 19:28 ` Jim Blandy
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=20080129180922.GK3773@caradoc.them.org \
--to=drow@false.org \
--cc=gdb-patches@sourceware.org \
--cc=jimb@codesourcery.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox