From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 17246 invoked by alias); 5 Dec 2002 21:42:24 -0000 Mailing-List: contact gdb-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sources.redhat.com Received: (qmail 17196 invoked from network); 5 Dec 2002 21:42:23 -0000 Received: from unknown (HELO crack.them.org) (65.125.64.184) by sources.redhat.com with SMTP; 5 Dec 2002 21:42: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 18K5dl-0002Mp-00; Thu, 05 Dec 2002 17:42:45 -0600 Received: from drow by nevyn.them.org with local (Exim 3.36 #1 (Debian)) id 18K3lj-0005Q2-00; Thu, 05 Dec 2002 16:42:51 -0500 Date: Thu, 05 Dec 2002 13:42:00 -0000 From: Daniel Jacobowitz To: David Carlton Cc: gdb , Andrew Cagney Subject: Re: store.exp failures Message-ID: <20021205214251.GA20762@nevyn.them.org> Mail-Followup-To: David Carlton , gdb , Andrew Cagney References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.1i X-SW-Source: 2002-12/txt/msg00092.txt.bz2 On Thu, Dec 05, 2002 at 01:30:54PM -0800, David Carlton wrote: > When I run gdb.base/store.exp, (GCC 3.1, i686 Linux) I get tons and > tons of failures. Looking into the log file, I see the following: > > (gdb) break main > Breakpoint 1 at 0x80488f0: file gdb.base/store.c, line 233. > (gdb) run > Starting program: /extra/gdb/mirror/src/gdb/testsuite/gdb.base/store > > Breakpoint 1, main () at gdb.base/store.c:233 > 233 wack_struct_1 (); > (gdb) tbreak wack_char > Breakpoint 2 at 0x804849e: file gdb.base/store.c, line 46. > (gdb) PASS: gdb.base/store.exp: tbreak wack_char > continue > Continuing. > > Program exited normally. > > So, basically, it looks like some of the calls to the wack_XXX > functions are getting optimized out by the compiler, even though no > optimization flags are being passed. Digging into the assembly > confirms this; the code for main starts off as follows: Make the function non-static and it should work as expected... -- Daniel Jacobowitz MontaVista Software Debian GNU/Linux Developer