From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 13092 invoked by alias); 23 Aug 2002 20:32:24 -0000 Mailing-List: contact gdb-patches-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sources.redhat.com Received: (qmail 13085 invoked from network); 23 Aug 2002 20:32:23 -0000 Received: from unknown (HELO crack.them.org) (65.125.64.184) by sources.redhat.com with SMTP; 23 Aug 2002 20:32:23 -0000 Received: from nevyn.them.org ([66.93.61.169] ident=mail) by crack.them.org with asmtp (Exim 3.12 #1 (Debian)) id 17iL6Y-0001zX-00; Fri, 23 Aug 2002 15:32:27 -0500 Received: from drow by nevyn.them.org with local (Exim 3.35 #1 (Debian)) id 17iL7E-0008ET-00; Fri, 23 Aug 2002 16:33:08 -0400 Date: Fri, 23 Aug 2002 14:08:00 -0000 From: Daniel Jacobowitz To: Michael Snyder , gdb-patches@sources.redhat.com Subject: Re: RFA (threads testsuite): More thread tests Message-ID: <20020823203308.GB30960@nevyn.them.org> Mail-Followup-To: Michael Snyder , gdb-patches@sources.redhat.com References: <20020709154033.GA7204@nevyn.them.org> <3D65751B.98E850BA@redhat.com> <20020823013447.GA18835@nevyn.them.org> <3D66843D.99DC8A49@redhat.com> <20020823190254.GA26364@nevyn.them.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20020823190254.GA26364@nevyn.them.org> User-Agent: Mutt/1.5.1i X-SW-Source: 2002-08/txt/msg00772.txt.bz2 On Fri, Aug 23, 2002 at 03:02:54PM -0400, Daniel Jacobowitz wrote: > On Fri, Aug 23, 2002 at 11:51:41AM -0700, Michael Snyder wrote: > > Daniel Jacobowitz wrote: > > > > > > On Thu, Aug 22, 2002 at 04:34:51PM -0700, Michael Snyder wrote: > > > > Daniel Jacobowitz wrote: > > > > > > > > > > Here's two tests I had lying around from when I developed the gdbserver > > > > > threads support. Gdbserver passes them with flying colors (if you use my > > > > > other patch which lets gdbserver run tests properly). GDB shows a couple of > > > > > problems, unpredictably (not always repeatable). > > > > > > > > > > OK to add these? > > > > > > > > Hi Joel, > > > > > > > > I understand the point of schedlock.exp, but what's the point of > > > > print-threads.exp? What is it that you're testing? > > > > > > No specific feature - just the general ability to handle threads doing > > > things. It has a slightly different behavior pattern than the other > > > threads testscases, and triggered different problems. Oh, and I > > > remember - there is no other testcase in the testsuite with > > > pthread_join in it; no threads ever actually exit. I found some > > > problems there while I was implementing the gdbserver threads support. > > > > OK, then, since we definitely need more thread testing, > > let's accept these. I like the way you verified that > > schedlock was implemented for the target before testing it. > > > > BTW, do these really have to be native-only? They should > > work for embedded pthread targets, shouldn't they? > > (And I'll make them use the new compile command too!) No, I won't, it isn't committed yet :). > Sure. But which ones will it work on, that's the question. I'm > tempted to have a gdb_skip_threads_test, but not sure what to key it > off of... I've committed them without the isnative check. Now they'll run anywhere they link. For the cases where GDB doesn't handle that... we'll have to find some way to suppress them. -- Daniel Jacobowitz MontaVista Software Debian GNU/Linux Developer