From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 10247 invoked by alias); 16 Nov 2006 21:53:10 -0000 Received: (qmail 10229 invoked by uid 22791); 16 Nov 2006 21:53:08 -0000 X-Spam-Check-By: sourceware.org Received: from imo-m19.mx.aol.com (HELO imo-m19.mx.aol.com) (64.12.137.11) by sourceware.org (qpsmtpd/0.31) with ESMTP; Thu, 16 Nov 2006 21:52:57 +0000 Received: from Jbbachky@aim.com by imo-m19.mx.aol.com (mail_out_v38_r7.6.) id o.cf7.219f56f (57870) for ; Thu, 16 Nov 2006 16:52:47 -0500 (EST) Received: from mblk-d23 (mblk-d23.mblk.aol.com [205.188.149.15]) by air-ia01.mail.aol.com (v114.2) with ESMTP id MAILINIA14-e20e455cddae239; Thu, 16 Nov 2006 16:52:47 -0500 References: <8C8D6E7E15FE5F6-5D0-723B@mblk-d22.sysops.aol.com> <20061115164953.GA31009@nevyn.them.org> To: gdb@sources.redhat.com Content-Transfer-Encoding: 7bit Subject: Re: gdbserver/gdb-6/4 and lots of pthreads Date: Thu, 16 Nov 2006 21:53:00 -0000 In-Reply-To: <20061115164953.GA31009@nevyn.them.org> X-MB-Message-Source: WebUI MIME-Version: 1.0 From: jbbachky@aim.com X-MB-Message-Type: User Content-Type: text/plain; charset="us-ascii"; format=flowed X-Mailer: AIM WebMail 22250 Received: from 192.146.101.24 by mblk-d23.sysops.aol.com (205.188.149.15) with HTTP (WebMailUI); Thu, 16 Nov 2006 16:52:47 -0500 Message-Id: <8C8D7E0B004BE30-C20-26F0@mblk-d23.sysops.aol.com> X-AOL-IP: 205.188.149.15 Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org X-SW-Source: 2006-11/txt/msg00115.txt.bz2 After working through a couple of configure bugs (configure #defines HAVE_TD_THR_TLS_GET_ADDR to 1 even when the test properly fails), I still seem to have the same symptoms. I have noticed that I now hit the default clause in the ptrace system call handler a few times - because there is not a case for PTRACE_GETSIGINFO in linux 2.6.10). Is this a/the problem? In the mean time, I'll trying to locate a definition for that case and make it work on my architectures. Daniel, is any settings and/or initialization things that I need to do in order to make use of your patch? Thanks again, John >-----Original Message----- >From: drow@false.org >To: jbbachky@aim.com >Cc: gdb@sources.redhat.com >Sent: Wed, 15 Nov 2006 11:49 AM >Subject: Re: gdbserver/gdb-6/4 and lots of pthreads > >On Wed, Nov 15, 2006 at 11:11:45AM -0500, jbbachky@aim.com wrote: >> Gdbserver attaches to my main thread and opens a socket, and then after >> invoking gdb and specifying my remote target, I select the particular >> thread that I wish to debug. Info threads shows all of my threads, and >> I see that gdbserver now attaches to all of them. > >Normally this is a feature :-) > >> Any attempt to single-step or continue with a breakpoint results in a >> "thrashing system". A counter in my context switching code shows almost >> 150k switchs/second, up from about 1200/sec when not attached with gdb. >> One of the 40 pthreads handle a 10ms SIGALRM. Almost all of the others >> are waiting for messages. > >It'll be the 10ms SIGALRM. Fortunately, I have _just_ the thing for >you. If you can wait another day or two, I expect to commit a patch >which dramatically improves gdbserver performance for multithreaded >applications with signals ignored by GDB. You can find the patch on >the gdb-patches list archives if you want to try it in the mean time; >it should apply to a checkout of current CVS HEAD. You need a patched >gdbserver and gdb client. > >-- >Daniel Jacobowitz >CodeSourcery ________________________________________________________________________ Check Out the new free AIM(R) Mail -- 2 GB of storage and industry-leading spam and email virus protection.