From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 1023 invoked by alias); 7 Jan 2007 17:00:33 -0000 Received: (qmail 1013 invoked by uid 22791); 7 Jan 2007 17:00:32 -0000 X-Spam-Check-By: sourceware.org Received: from nf-out-0910.google.com (HELO nf-out-0910.google.com) (64.233.182.184) by sourceware.org (qpsmtpd/0.31) with ESMTP; Sun, 07 Jan 2007 17:00:28 +0000 Received: by nf-out-0910.google.com with SMTP id n28so23849nfc for ; Sun, 07 Jan 2007 09:00:26 -0800 (PST) Received: by 10.82.118.2 with SMTP id q2mr2529809buc.1168189226084; Sun, 07 Jan 2007 09:00:26 -0800 (PST) Received: by 10.82.168.9 with HTTP; Sun, 7 Jan 2007 09:00:26 -0800 (PST) Message-ID: <9560bc3b0701070900q515a8c5cu1f539506d4018c06@mail.gmail.com> Date: Sun, 07 Jan 2007 17:00:00 -0000 From: "Yaki Tebeka" To: "Jim Blandy" Subject: Re: Resuming a single suspended thread on Linux Cc: gdb@sourceware.org In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <9560bc3b0701061449s6d240616o788d93f472a578b8@mail.gmail.com> Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org X-SW-Source: 2007-01/txt/msg00111.txt.bz2 Hi Jim Thanks for the suggested solution. I read the "set scheduler-locking" feature documentation few times (http://sourceware.org/gdb/current/onlinedocs/gdb_6.html#IDX281) and I must admit that I am not quite sure that I understand it correctly... One of it sentences says that the other threads are "completely free to run when you use commands like `continue', `until', or `finish'". If I understand this correctly, it will not help in my case. Please let me know if I didn't understand this mechanism correctly. Yaki On 1/7/07, Jim Blandy wrote: > > "Yaki Tebeka" 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. > -- Yaki Tebeka