From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 13678 invoked by alias); 2 Mar 2002 19:10:52 -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 13571 invoked from network); 2 Mar 2002 19:10:51 -0000 Received: from unknown (HELO fred.ninemoons.com) (68.15.182.197) by sources.redhat.com with SMTP; 2 Mar 2002 19:10:51 -0000 Received: (from fnf@localhost) by fred.ninemoons.com (8.11.6/8.11.6) id g22JA8P04673; Sat, 2 Mar 2002 12:10:08 -0700 From: Fred Fish Message-Id: <200203021910.g22JA8P04673@fred.ninemoons.com> Subject: [RFC] xfail a break.exp test for remote targets To: gdb-patches@sources.redhat.com Date: Sat, 02 Mar 2002 11:10:00 -0000 Cc: fnf@redhat.com Reply-To: fnf@redhat.com X-Mailer: ELM [version 2.5 PL6] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-SW-Source: 2002-03/txt/msg00011.txt.bz2 I just posted a fairly long analysis to the gdb-bug list about how remote targets can miss breakpoints internal to a line or fail to print the breakpoint info for a breakpoint at the end of a stepping range, when single stepping over a source line. This patch will fix the testsuite failure until the remote/native difference in resuming execution in the single step case can be resolved. Comments? -Fred 2002-03-02 Fred Fish * gdb.base/break.exp: Setup xfail for remote targets for the "step onto breakpoint" due to the way remote targets handle breakpoints at the end of a stepping range. Index: gdb.base/break.exp =================================================================== RCS file: /cvs/cvsfiles/devo/gdb/testsuite/gdb.base/break.exp,v retrieving revision 1.65 diff -c -p -r1.65 break.exp *** break.exp 2002/01/13 00:32:27 1.65 --- break.exp 2002/03/02 18:50:04 *************** gdb_test "break +1" \ *** 222,227 **** --- 222,237 ---- # Check to see if breakpoint is hit when stepped onto + # This will always fail for remote targets that step over the entire + # source line in one operation local to the target because gdb won't + # have breakpoints inserted for the first single step and thus won't + # print the breakpoint at the location it stops at after stepping. + # Note that removing the current stopped-at breakpoint (number 5) would + # cause this test to succeed. Perhaps we should try it both ways. + if [is_remote target] { + setup_xfail "*-*-*" + } + gdb_test "step" \ ".*Breakpoint \[0-9\]+, main \\(argc=.*, argv=.*, envp=.*\\) at .*$srcfile:86.*86\[\t \]+return argc;" \ "step onto breakpoint"