From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 29391 invoked by alias); 19 Mar 2004 20:12:43 -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 29375 invoked from network); 19 Mar 2004 20:12:41 -0000 Received: from unknown (HELO localhost.redhat.com) (66.30.197.194) by sources.redhat.com with SMTP; 19 Mar 2004 20:12:41 -0000 Received: from redhat.com (localhost [127.0.0.1]) by localhost.redhat.com (Postfix) with ESMTP id 2EC7A2B92; Fri, 19 Mar 2004 15:12:40 -0500 (EST) Message-ID: <405B5437.4010801@redhat.com> Date: Sat, 20 Mar 2004 07:00:00 -0000 From: Andrew Cagney User-Agent: Mozilla/5.0 (X11; U; NetBSD macppc; en-GB; rv:1.4.1) Gecko/20040217 MIME-Version: 1.0 To: Kip Macy Cc: mrdavid@leaf.lumiere.net, gdb@sources.redhat.com Subject: Re: gdb with bigger than 2G 32bit core files References: <20040319101508.Y66700-100000@leaf.lumiere.net> <20040319104231.F12147@demos.bsdclusters.com> In-Reply-To: <20040319104231.F12147@demos.bsdclusters.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2004-03/txt/msg00189.txt.bz2 > Yes. You need: > --enable-64-bit-bfd With GDB 6.1 you don't need that. With 6.0, you'd be wasting your time - the 6.0 code base doesn't use fseek64 et.al. For reference there's a testcase (bigcore.exp) that is known to pass on certain GNU/Linux variants (RHEL for instance). Andrew >>> >>> hi, >>> >>> has anyone been able to analyze bigger than 2 gig core files? >>> >>> i am trying to analyze core files produced by a 32bit x86 linux 2.4 box >>> with the O_LARGEFILE core patch like this : >>> >>> file = filp_open(corename, O_CREAT | 2 | O_NOFOLLOW | O_LARGEFILE, 0600); >>> >>> i know it can be done with linux 2.6 on 64bit arch box... >>> >>> >>> >>> ~david