From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gdb-return-27362-listarch-gdb=sources.redhat.com@sourceware.org>
Received: (qmail 14502 invoked by alias); 7 Jan 2007 14:59:36 -0000
Received: (qmail 14494 invoked by uid 22791); 7 Jan 2007 14:59:35 -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; Sun, 07 Jan 2007 14:59:31 +0000
Received: (qmail 14635 invoked from network); 7 Jan 2007 14:59:29 -0000
Received: from unknown (HELO localhost) (jimb@127.0.0.2)   by mail.codesourcery.com with ESMTPA; 7 Jan 2007 14:59:29 -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>
From: Jim Blandy <jimb@codesourcery.com>
Date: Sun, 07 Jan 2007 14:59:00 -0000
In-Reply-To: <9560bc3b0701061449s6d240616o788d93f472a578b8@mail.gmail.com> (Yaki Tebeka's message of "Sun, 7 Jan 2007 00:49:50 +0200")
Message-ID: <m3vejiriff.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/msg00110.txt.bz2


"Yaki Tebeka" <tebeka@gmail.com> writes:
> I am implementing a special purpose debugger using gdb.
> When a program is being debugged, I load into it a special library
> that runs a thread (inside the debugged process) that reports data to
> the debugger using a socket communication.
>
> This approach works well on Windows (with another debugger engine),
> but when I try to implement it using gdb on Linux, I realize that
> whenever the debugged application execution is suspended (breakpoint /
> etc), my data reporting thread, that runs inside the debugged process,
> is also suspended.
>
> I tried "thread apply X continue", but it seems to continue the entire
> process (which, as far as I understand, is the right behavior on
> Linux).
>
> Does anyone have an idea for a solution to my problem.

Hi --- have you looked at the documentation for 'set
scheduler-locking'?  That might work for you.