From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 25024 invoked by alias); 9 Jan 2004 16:56:08 -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 25016 invoked from network); 9 Jan 2004 16:56:07 -0000 Received: from unknown (HELO localhost.redhat.com) (216.129.200.20) by sources.redhat.com with SMTP; 9 Jan 2004 16:56:07 -0000 Received: from gnu.org (localhost [127.0.0.1]) by localhost.redhat.com (Postfix) with ESMTP id 275572B8F; Fri, 9 Jan 2004 11:56:07 -0500 (EST) Message-ID: <3FFEDD26.3080304@gnu.org> Date: Fri, 09 Jan 2004 16:56:00 -0000 From: Andrew Cagney User-Agent: Mozilla/5.0 (X11; U; NetBSD macppc; en-US; rv:1.0.2) Gecko/20030820 MIME-Version: 1.0 To: Eli Zaretskii , Michael Elizabeth Chastain , nathanw@wasabisystems.com Cc: gdb@sources.redhat.com Subject: Re: "break main; run" test References: <20040109031621.412084B35A@berman.michael-chastain.com> <2914-Fri09Jan2004104913+0200-eliz@elta.co.il> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2004-01/txt/msg00124.txt.bz2 FYI, the release process recommends the following smoke test: > 15.7.2 Sanity check the tar ball > > Pick a popular machine (Solaris/PPC?) and try the build on that. > > > > $ bunzip2 < gdb-5.2.tar.bz2 | tar xpf - > $ cd gdb-5.2 > $ ./configure > $ make > ... > $ ./gdb/gdb ./gdb/gdb > GNU gdb 5.2 > ... > (gdb) b main > Breakpoint 1 at 0x80732bc: file main.c, line 734. > (gdb) run > Starting program: /tmp/gdb-5.2/gdb/gdb > > Breakpoint 1, main (argc=1, argv=0xbffff8b4) at main.c:734 > 734 catch_errors (captured_main, &args, "", RETURN_MASK_ALL); > (gdb) print args > $1 = {argc = 136426532, argv = 0x821b7f0} > (gdb) Should note that I intend tweaking the doco so that "backtrace", instead of "print args" is used. I suspect that "backtrace" is GDB's second most popular user command (the first is "run") :-) Andrew >> Date: Thu, 8 Jan 2004 22:16:21 -0500 (EST) >> From: mec.gnu@mindspring.com (Michael Elizabeth Chastain) >> > >> > When people refer to the test of starting gdb on a program, setting a >> > breakpoint on "main", and running to that point, is there a particular >> > standard test program in mind? "Hello world"? The GDB binary itself? > >> >> You are right; it is ambiguous. > > > Seconded. Perhaps we should replace that language with something less > ambiguous. > > >> To me, it usually means "the gdb binary itself", since the gdb binary is >> a large program and it's guaranteed to exist. Sometimes it means >> "hello world", and sometimes it means "any random program". > > > It should IMHO preferably be some non-trivially large program, as some > subtle problems don't get expiosed unless GDB needs to deal with > complex debug info structures. It certainly cannot be a program with > no debug info, since then it's not guaranteed that GDB will know where > to find the symbol `main'. >