From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gdb-return-17643-listarch-gdb=sources.redhat.com@sources.redhat.com>
Received: (qmail 20092 invoked by alias); 17 Mar 2004 19:46:27 -0000
Mailing-List: contact gdb-help@sources.redhat.com; run by ezmlm
Precedence: bulk
List-Subscribe: <mailto:gdb-subscribe@sources.redhat.com>
List-Archive: <http://sources.redhat.com/ml/gdb/>
List-Post: <mailto:gdb@sources.redhat.com>
List-Help: <mailto:gdb-help@sources.redhat.com>, <http://sources.redhat.com/ml/#faqs>
Sender: gdb-owner@sources.redhat.com
Received: (qmail 20033 invoked from network); 17 Mar 2004 19:46:25 -0000
Received: from unknown (HELO pcsmail.patni.com) (203.124.139.197)
  by sources.redhat.com with SMTP; 17 Mar 2004 19:46:25 -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 i2HJnU206517
	for <gdb@sources.redhat.com>; Thu, 18 Mar 2004 01:19:30 +0530
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="utf-8"
Content-Transfer-Encoding: base64
Subject: BACKTRACE for coredump in signal handler does come proper for IA-64
Date: Wed, 17 Mar 2004 19:46:00 -0000
Message-ID: <374639AB1012AA4C840022842AA95BC2A738BA@ruby.patni.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
From: "Kotian, Deepak" <Deepak.Kotian@patni.com>
To: <gdb@sources.redhat.com>
X-SW-Source: 2004-03/txt/msg00159.txt.bz2

SGksDQoNCkJBQ0tUUkFDRSBmb3IgY29yZWR1bXAgaW4gc2lnbmFsIGhhbmRs
ZXIgZG9lcyBjb21lIHByb3BlciBmb3IgSUEtNjQuDQoNCkFueSBpbnB1dHMg
d2hhdCBpcyB0aGUgcmVhc29uIGZvciBpdCwgcGxlYXNlIGxldCBtZSBrbm93
Lg0KDQpUaGFua3MgYW5kIFJlZ2FyZHMNCg0KRGVlcGFrDQoNCiANCg0KIA0K
DQo=
>From gdb-return-17644-listarch-gdb=sources.redhat.com@sources.redhat.com Wed Mar 17 21:10:45 2004
Return-Path: <gdb-return-17644-listarch-gdb=sources.redhat.com@sources.redhat.com>
Delivered-To: listarch-gdb@sources.redhat.com
Received: (qmail 16036 invoked by alias); 17 Mar 2004 21:10:45 -0000
Mailing-List: contact gdb-help@sources.redhat.com; run by ezmlm
Precedence: bulk
List-Subscribe: <mailto:gdb-subscribe@sources.redhat.com>
List-Archive: <http://sources.redhat.com/ml/gdb/>
List-Post: <mailto:gdb@sources.redhat.com>
List-Help: <mailto:gdb-help@sources.redhat.com>, <http://sources.redhat.com/ml/#faqs>
Sender: gdb-owner@sources.redhat.com
Delivered-To: mailing list gdb@sources.redhat.com
Received: (qmail 16028 invoked from network); 17 Mar 2004 21:10:44 -0000
Received: from unknown (HELO hawaii.kealia.com) (209.3.10.89)
  by sources.redhat.com with SMTP; 17 Mar 2004 21:10:44 -0000
Received: by hawaii.kealia.com (Postfix, from userid 2049)
	id D5654C553; Wed, 17 Mar 2004 13:10:43 -0800 (PST)
To: gdb <gdb@sources.redhat.com>
Subject: gdb and truncated core files
From: David Carlton <carlton@kealia.com>
Date: Wed, 17 Mar 2004 21:10:00 -0000
Message-ID: <yf2ad2fxjqk.fsf@hawaii.kealia.com>
User-Agent: Gnus/5.1002 (Gnus v5.10.2) XEmacs/21.4 (Reasonable Discussion,
 linux)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-SW-Source: 2004-03/txt/msg00160.txt.bz2
Content-length: 305

Is there any way for GDB (on i686-pc-linux-gnu) to tell whether or not
a core file has been truncated?  We have a habit of generating
truncated core files around here, and it would be nice if there were
an easy way to tell whether or not a given core file is truncated.

David Carlton
carlton@kealia.com