From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 4826 invoked by alias); 30 Jan 2008 17:56:47 -0000 Received: (qmail 4818 invoked by uid 22791); 30 Jan 2008 17:56:47 -0000 X-Spam-Check-By: sourceware.org Received: from py-out-1112.google.com (HELO py-out-1112.google.com) (64.233.166.180) by sourceware.org (qpsmtpd/0.31) with ESMTP; Wed, 30 Jan 2008 17:56:24 +0000 Received: by py-out-1112.google.com with SMTP id v53so383398pyh.33 for ; Wed, 30 Jan 2008 09:56:22 -0800 (PST) Received: by 10.35.63.2 with SMTP id q2mr1123996pyk.49.1201715781999; Wed, 30 Jan 2008 09:56:21 -0800 (PST) Received: by 10.35.36.15 with HTTP; Wed, 30 Jan 2008 09:56:21 -0800 (PST) Message-ID: <8f2776cb0801300956q276d3cdahcc6fe3855983b8c@mail.gmail.com> Date: Wed, 30 Jan 2008 17:56:00 -0000 From: "Jim Blandy" To: "M R Swami Reddy" Subject: Re: gdb testsuite Cc: gdb@sourceware.org In-Reply-To: <47A073FD.9060103@nsc.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <4799B660.2080905@nsc.com> <8f2776cb0801251016y1a4cfbcfp35fab5ecacee8b1d@mail.gmail.com> <479D62DA.4080100@nsc.com> <8f2776cb0801281050w4ae2d83fw53b793ba633302e1@mail.gmail.com> <479EC263.3060107@nsc.com> <8f2776cb0801291221g106e39acw493a3b9e0a8e7798@mail.gmail.com> <47A073FD.9060103@nsc.com> X-Google-Sender-Auth: be3f8d565e5a4112 X-IsSubscribed: yes Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org X-SW-Source: 2008-01/txt/msg00341.txt.bz2 It's not obvious to me where the -lm comes from. gdb/testsuite/lib contains a number of files that are also involved in running the tests; in particular, gdb_compile is defined in gdb/testsuite/lib/gdb.exp. One unfortunate characteristic of the GDB test suite is that, even if GDB is horribly broken, many tests will still pass. You can't have much confidence that things are basically working with 356 failures. You should look through gdb.log and work through a bunch of them to get a feel for the state of things. If you're going to do any significant amount of work with the test suite, I would recommend investing a little time in learning the Tcl language. It's built on some very simple concepts, and knowing how those actually work, instead of guessing based on the resemblance between Tcl and more familiar languages, will save confusion in the future. I think there are tutorials on-line somewhere.