From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gdb-patches-return-53681-listarch-gdb-patches=sources.redhat.com@sourceware.org>
Received: (qmail 3898 invoked by alias); 29 Jan 2008 19:21:57 -0000
Received: (qmail 3888 invoked by uid 22791); 29 Jan 2008 19:21:57 -0000
X-Spam-Check-By: sourceware.org
Received: from py-out-1112.google.com (HELO py-out-1112.google.com) (64.233.166.176)     by sourceware.org (qpsmtpd/0.31) with ESMTP; Tue, 29 Jan 2008 19:21:35 +0000
Received: by py-out-1112.google.com with SMTP id v53so2569248pyh.33         for <gdb-patches@sourceware.org>; Tue, 29 Jan 2008 11:21:32 -0800 (PST)
Received: by 10.35.60.15 with SMTP id n15mr8312738pyk.33.1201634492207;         Tue, 29 Jan 2008 11:21:32 -0800 (PST)
Received: by 10.35.36.15 with HTTP; Tue, 29 Jan 2008 11:21:32 -0800 (PST)
Message-ID: <8f2776cb0801291121i46404195udb5e9f0d99becd41@mail.gmail.com>
Date: Tue, 29 Jan 2008 19:28:00 -0000
From: "Jim Blandy" <jimb@red-bean.com>
To: "Jim Blandy" <jimb@codesourcery.com>, gdb-patches@sourceware.org
Subject: Re: RFA: Make sigthread.exp more reliable
In-Reply-To: <20080129180922.GK3773@caradoc.them.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <m33at3vng0.fsf@codesourcery.com> 	 <20080129180922.GK3773@caradoc.them.org>
X-Google-Sender-Auth: 523eee2539e96770
X-IsSubscribed: yes
Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-patches.sourceware.org>
List-Subscribe: <mailto:gdb-patches-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-patches/>
List-Post: <mailto:gdb-patches@sourceware.org>
List-Help: <mailto:gdb-patches-help@sourceware.org>, <http://sourceware.org/ml/#faqs>
Sender: gdb-patches-owner@sourceware.org
X-SW-Source: 2008-01/txt/msg00713.txt.bz2

On Jan 29, 2008 10:09 AM, Daniel Jacobowitz <drow@false.org> wrote:
> 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!

Committed --- thanks!