From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gdb-return-27537-listarch-gdb=sources.redhat.com@sourceware.org>
Received: (qmail 31398 invoked by alias); 18 Jan 2007 18:36:02 -0000
Received: (qmail 31384 invoked by uid 22791); 18 Jan 2007 18:36:01 -0000
X-Spam-Check-By: sourceware.org
Received: from mail.codesourcery.com (HELO mail.codesourcery.com) (65.74.133.4)     by sourceware.org (qpsmtpd/0.31) with ESMTP; Thu, 18 Jan 2007 18:35:55 +0000
Received: (qmail 6504 invoked from network); 18 Jan 2007 18:35:53 -0000
Received: from unknown (HELO localhost) (jimb@127.0.0.2)   by mail.codesourcery.com with ESMTPA; 18 Jan 2007 18:35:53 -0000
To: "Yaki Tebeka" <tebeka@gmail.com>
Cc: gdb@sourceware.org
Subject: Re: Resuming a single suspended thread on Linux
References: <9560bc3b0701061449s6d240616o788d93f472a578b8@mail.gmail.com> 	<m3vejiriff.fsf@codesourcery.com> 	<9560bc3b0701070900q515a8c5cu1f539506d4018c06@mail.gmail.com> 	<20070107233002.GA28520@nevyn.them.org> 	<9560bc3b0701150147s793b9f97y44ba89fb6e72b350@mail.gmail.com>
From: Jim Blandy <jimb@codesourcery.com>
Date: Thu, 18 Jan 2007 18:36:00 -0000
In-Reply-To: <9560bc3b0701150147s793b9f97y44ba89fb6e72b350@mail.gmail.com> (Yaki Tebeka's message of "Mon, 15 Jan 2007 11:47:37 +0200")
Message-ID: <m3y7o09o8i.fsf@codesourcery.com>
User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/22.0.50 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-IsSubscribed: yes
Mailing-List: contact gdb-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb.sourceware.org>
List-Subscribe: <mailto:gdb-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb/>
List-Post: <mailto:gdb@sourceware.org>
List-Help: <mailto:gdb-help@sourceware.org>, <http://sourceware.org/ml/#faqs>
Sender: gdb-owner@sourceware.org
X-SW-Source: 2007-01/txt/msg00285.txt.bz2

"Yaki Tebeka" <tebeka@gmail.com> writes:
> I tried the suggested solution, but unfortunately, it does not seem to work.
> I am running Fedora Core 5, 64 bit on an AMD processor.
> After I call "set scheduler-locking on", and "continue", the entire
> debugged process seem to remain freeze.
> I tried setting my data collection thread as the active thread and
> even setting the main thread as the active thread, but both options
> does not seem to work.
>
> Do you know if its a GDB bug, or an "expected behaviour" on Linux?
>
> Can you suggest another solution to my problem?

Without knowing more, I couldn't say.

Does the thread you're running wait on any mutexes that might be held
by the stopped threads?