From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 27213 invoked by alias); 11 Dec 2002 22:15:56 -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 27205 invoked from network); 11 Dec 2002 22:15:55 -0000 Received: from unknown (HELO duracef.shout.net) (204.253.184.12) by sources.redhat.com with SMTP; 11 Dec 2002 22:15:55 -0000 Received: (from mec@localhost) by duracef.shout.net (8.11.6/8.11.6) id gBBMFqh08988; Wed, 11 Dec 2002 16:15:52 -0600 Date: Wed, 11 Dec 2002 14:19:00 -0000 From: Michael Elizabeth Chastain Message-Id: <200212112215.gBBMFqh08988@duracef.shout.net> To: carlton@math.stanford.edu, gdb-patches@sources.redhat.com Subject: Re: [rfa/testsuite] gdb.base/selftest.exp: work with optimization Cc: fnasser@redhat.com X-SW-Source: 2002-12/txt/msg00376.txt.bz2 David Carlton writes: > Digging further, it happens during the part of the test that steps > through captured_main; when GDB is compiled with optimization, GDB > sometimes stops on the opening brace. I see that too. gdb.base/selftest.exp needs to be a lot more careful about its regexp's, because it is operating on a test program which changes outside of its control, rather than a small defined test program. + # "current_directory initialization" possibilities happen to + # me with GCC 3.1 on i686-pc-linux-gnu when I compile with + # optimization. That is twice today you said "gcc 3.1" -- is that a think for gcc 3.2.1, or are you really testing with gcc 3.1? Michael C