From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 20780 invoked by alias); 23 Nov 2004 23:16:05 -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 20749 invoked from network); 23 Nov 2004 23:16:00 -0000 Received: from unknown (HELO pippin.tausq.org) (64.81.244.94) by sourceware.org with SMTP; 23 Nov 2004 23:16:00 -0000 Received: by pippin.tausq.org (Postfix, from userid 1000) id 06EE7CD650; Tue, 23 Nov 2004 15:16:00 -0800 (PST) Date: Tue, 23 Nov 2004 23:16:00 -0000 From: Randolph Chung To: gdb-patches@sources.redhat.com Subject: [patch/rfa] fix thread_check test Message-ID: <20041123231559.GV9148@tausq.org> Reply-To: Randolph Chung Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline X-GPG: for GPG key, see http://www.tausq.org/gpg.txt User-Agent: Mutt/1.5.5.1+cvs20040105i X-SW-Source: 2004-11/txt/msg00458.txt.bz2 i don't think this has ever worked for anybody... :) The test program name in this test case doesn't match what's in the testsuite. The regular expression was wrong as well. Patch tested on hppa-linux. ok to check in? this should give (almost) everbody 2 more PASSes on their testsuite results. randolph 2004-11-23 Randolph Chung testsuite/ * gdb.threads/thread_check.exp: Use $srcfile for test program name instead of "tbug". Fix regexp to work properly with gdb_test. Index: testsuite/gdb.threads/thread_check.exp =================================================================== RCS file: /cvs/src/src/gdb/testsuite/gdb.threads/thread_check.exp,v retrieving revision 1.1 diff -u -p -r1.1 thread_check.exp --- testsuite/gdb.threads/thread_check.exp 31 Aug 2004 20:01:13 -0000 1.1 +++ testsuite/gdb.threads/thread_check.exp 23 Nov 2004 23:13:27 -0000 @@ -27,7 +27,7 @@ # in ptrace system call. # # Test Strategy: -# - tbug.c creates 2 threads +# - thread_check.c creates 2 threads # - start gdb # - create 2 breakpoints #1 main() #2 tf() (the thread function) # - run gdb till #1 main() breakpoint is reached @@ -74,14 +74,14 @@ gdb_test "break tf" \ # continue to tf() breakpoint #2 # gdb_test "continue" \ - ".*Breakpoint 2.*tf.* at .*tbug.* .*\r\n.*$gdb_prompt $" \ + ".*Breakpoint 2,.*tf.*at.*$srcfile:.*" \ "continue to tf" # # backtrace from thread function. # gdb_test "backtrace" \ - "#0 .*tf .*at .*tbug.*" \ + "#0 .*tf .*at .*$srcfile:.*" \ "backtrace from thread function" -- Randolph Chung Debian GNU/Linux Developer, hppa/ia64 ports http://www.tausq.org/