From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 7368 invoked by alias); 17 Aug 2004 13:48:14 -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 7361 invoked from network); 17 Aug 2004 13:48:13 -0000 Received: from unknown (HELO granger.mail.mindspring.net) (207.69.200.148) by sourceware.org with SMTP; 17 Aug 2004 13:48:13 -0000 Received: from user-119a90a.biz.mindspring.com ([66.149.36.10] helo=berman.michael-chastain.com) by granger.mail.mindspring.net with esmtp (Exim 3.33 #1) id 1Bx4Ju-0007uK-00; Tue, 17 Aug 2004 09:48:10 -0400 Received: from mindspring.com (localhost [127.0.0.1]) by berman.michael-chastain.com (Postfix) with SMTP id AF0664B102; Tue, 17 Aug 2004 09:48:09 -0400 (EDT) Date: Tue, 17 Aug 2004 13:48:00 -0000 From: Michael Chastain To: drow@false.org, david@streamline-computing.com Subject: Re: Opteron Stack Woes Cc: gdb@sources.redhat.com Message-ID: <41220C98.nailNAQ1TW4UF@mindspring.com> References: <1092744111.3127.25.camel@cpc4-oxfd5-5-0-cust12.oxfd.cable.ntl.com> <20040817131057.GA7719@nevyn.them.org> In-Reply-To: <20040817131057.GA7719@nevyn.them.org> User-Agent: nail 10.8 6/28/04 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-SW-Source: 2004-08/txt/msg00228.txt.bz2 > You might want to investigate why the backtrace didn't stop earlier, at > main or at a fortran entry point. GDB may be confused about > main_name(). This hit me too when I tried to write the first fortran program for the test suite. I haven't filed a PR yet, but gdb is clueless about main_name for fortran programs compiled with g77 3.4.1, both dwarf-2 and stabs+. When I say 'start', gdb puts the breakpoint in function 'main' in the fortran runtime library, not at the 'program' statement. The only call to set_main_name in gdb is in dbxread.c and it's not getting called. I don't see any N_MAIN stab line in hello.s, so g77 3.4.1 isn't doing what we want. Note that David is using a different fortran compiler. I don't know why David's stack trace blows right through main.