From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 32610 invoked by alias); 19 Mar 2004 17:59:31 -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 32592 invoked from network); 19 Mar 2004 17:59:29 -0000 Received: from unknown (HELO pcsmail.patni.com) (203.124.139.197) by sources.redhat.com with SMTP; 19 Mar 2004 17:59:29 -0000 Received: from ruby.patni.com (ruby.patni.com [204.165.186.9]) by pcsmail.patni.com (8.11.6/8.9.3) with ESMTP id i2JI2HM29817 for ; Fri, 19 Mar 2004 23:32:17 +0530 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 Subject: RE: BACKTRACE for coredump in signal handler does come proper for IA-64 Date: Fri, 19 Mar 2004 20:12:00 -0000 Message-ID: <374639AB1012AA4C840022842AA95BC2A738BC@ruby.patni.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Priority: Urgent From: "Kotian, Deepak" To: "Kotian, Deepak" , X-SW-Source: 2004-03/txt/msg00186.txt.bz2 SGkgLA0KIA0KQ291bGQgb25lIHBsZWFzZSBnaXZlIGEgdmlldyBvbiB0aGlz IGFzIHNvb24gYXMgcG9zc2libGUuDQogDQpUaGFua3MgYW5kIFJlZ2FyZHMN CkRlZXBhaw0KIA0KDQoJLS0tLS1PcmlnaW5hbCBNZXNzYWdlLS0tLS0gDQoJ RnJvbTogS290aWFuLCBEZWVwYWsgDQoJU2VudDogVGh1IDMvMTgvMjAwNCAx OjIxIEFNIA0KCVRvOiBnZGJAc291cmNlcy5yZWRoYXQuY29tIA0KCUNjOiAN CglTdWJqZWN0OiBCQUNLVFJBQ0UgZm9yIGNvcmVkdW1wIGluIHNpZ25hbCBo YW5kbGVyIGRvZXMgY29tZSBwcm9wZXIgZm9yIElBLTY0DQoJDQoJDQoNCglI aSwNCg0KCUJBQ0tUUkFDRSBmb3IgY29yZWR1bXAgaW4gc2lnbmFsIGhhbmRs ZXIgZG9lcyBjb21lIHByb3BlciBmb3IgSUEtNjQuDQoNCglBbnkgaW5wdXRz IHdoYXQgaXMgdGhlIHJlYXNvbiBmb3IgaXQsIHBsZWFzZSBsZXQgbWUga25v dy4NCg0KCVRoYW5rcyBhbmQgUmVnYXJkcw0KDQoJRGVlcGFrDQoNCgkgDQoN CgkgDQoNCg== >From gdb-return-17671-listarch-gdb=sources.redhat.com@sources.redhat.com Fri Mar 19 18:31:16 2004 Return-Path: Delivered-To: listarch-gdb@sources.redhat.com Received: (qmail 21736 invoked by alias); 19 Mar 2004 18:31: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 Delivered-To: mailing list gdb@sources.redhat.com Received: (qmail 21674 invoked from network); 19 Mar 2004 18:31:13 -0000 Received: from unknown (HELO tetris.eyetide.com) (209.133.65.209) by sources.redhat.com with SMTP; 19 Mar 2004 18:31:13 -0000 Received: from localhost (localhost [127.0.0.1]) by tetris.eyetide.com (Postfix) with ESMTP id C0EDE9358E for ; Fri, 19 Mar 2004 10:31:11 -0800 (PST) Received: from tetris.eyetide.com ([127.0.0.1]) by localhost (tetris.eyetide.com [127.0.0.1]) (amavisd-new, port 10024) with SMTP id 98033-17 for ; Fri, 19 Mar 2004 10:31:10 -0800 (PST) Received: from leaf.lumiere.net (unknown [209.133.65.222]) by tetris.eyetide.com (Postfix) with ESMTP id D1818933C7 for ; Fri, 19 Mar 2004 10:31:10 -0800 (PST) Received: by leaf.lumiere.net (Postfix, from userid 1007) id 6E966CD26; Fri, 19 Mar 2004 10:31:10 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by leaf.lumiere.net (Postfix) with ESMTP id 6CFB83AE5 for ; Fri, 19 Mar 2004 10:31:10 -0800 (PST) Date: Fri, 19 Mar 2004 20:36:00 -0000 From: mrdavid@leaf.lumiere.net To: gdb@sources.redhat.com Subject: gdb with bigger than 2G 32bit core files Message-ID: <20040319101508.Y66700-100000@leaf.lumiere.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Virus-Scanned: by amavisd-new at eyetide.com X-SW-Source: 2004-03/txt/msg00187.txt.bz2 Content-length: 331 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