From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 16133 invoked by alias); 31 Dec 2006 20:49:55 -0000 Received: (qmail 16125 invoked by uid 22791); 31 Dec 2006 20:49:55 -0000 X-Spam-Check-By: sourceware.org Received: from nevyn.them.org (HELO nevyn.them.org) (66.93.172.17) by sourceware.org (qpsmtpd/0.31.1) with ESMTP; Sun, 31 Dec 2006 20:49:50 +0000 Received: from drow by nevyn.them.org with local (Exim 4.63) (envelope-from ) id 1H17cq-0006f6-4S; Sun, 31 Dec 2006 15:49:48 -0500 Date: Sun, 31 Dec 2006 20:49:00 -0000 From: Daniel Jacobowitz To: Mark Kettenis Cc: gdb-patches@sourceware.org Subject: Re: [commit] Testsuite updates Message-ID: <20061231204948.GA25548@nevyn.them.org> Mail-Followup-To: Mark Kettenis , gdb-patches@sourceware.org References: <20061231200905.GA24490@nevyn.them.org> <200612312035.kBVKZ0jI001086@brahms.sibelius.xs4all.nl> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200612312035.kBVKZ0jI001086@brahms.sibelius.xs4all.nl> User-Agent: Mutt/1.5.13 (2006-08-11) X-IsSubscribed: yes Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org X-SW-Source: 2006-12/txt/msg00421.txt.bz2 Sorry for batching updates like that; I'll be more verbose. On Sun, Dec 31, 2006 at 09:35:00PM +0100, Mark Kettenis wrote: > > I was using a HEAD build of glibc rather than the system's glibc, > > in order to pick up Jan's fix for unwinding information in signal > > handlers. Having debugging information for the C library caused the > > annota1.exp and annota3.exp failures. > > So continueing to printf didn't actually get is to printf? What's > going on here? We got to printf just fine. But, printf is really the exported name of __printf. If we have only the dynamic symbol table, backtrace will display printf; if we have debugging info, it will display __printf. There was already some accomodation for _printf in the tests. I think this is the work of strong_alias or attribute((alias)). > > The selftest.exp patch adds an XFAIL for a GCC bug in my system > > compiler, which I reported several months ago to the GCC bugzilla. > > I'm not optimistic about it getting fixed soon. > > A bug in *your* system compiler. How widespread is this bug? We > really should be careful with complicating tests to work around > problems in particular GCC versions. It's in every version of GCC after 4.0, for every platform. It's a pretty serious problem, too. Here's more information, if you're interested: http://gcc.gnu.org/bugzilla/show_bug.cgi?id=26475 We have an initialization of some variable to a constant. The internal representation does not keep track of the location of constants, so when it is optimized away on entry to SSA, there's no way to recover the location. And when it recreates the constant, it picks a most peculiar location for it (based on where the PHI nodes are). > > And finally, for linux-dp.exp, an omission in Nathan's recent change > > generated UNSUPPORTEDs on native GNU/Linux systems, where the test > > should pass. > > Can you elaborate? I mean, what output is genererated that should be > ignored? Output from the test program, rather than GDB. I believe Nathan was working on our ColdFire toolchains at the time, which means he was testing gdbserver - in which case the console output of linux-dp doesn't show up. But in a native configuration it's quite a noisy program. The pattern matches the status of the philosophers for each thread. -- Daniel Jacobowitz CodeSourcery