From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 28191 invoked by alias); 1 Nov 2004 21:20:16 -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 28172 invoked from network); 1 Nov 2004 21:20:14 -0000 Received: from unknown (HELO legolas.inter.net.il) (192.114.186.24) by sourceware.org with SMTP; 1 Nov 2004 21:20:14 -0000 Received: from zaretski ([80.230.159.47]) by legolas.inter.net.il (MOS 3.5.3-GR) with ESMTP id CZV16370 (AUTH halo1); Mon, 1 Nov 2004 23:18:28 +0200 (IST) Date: Mon, 01 Nov 2004 21:20:00 -0000 From: "Eli Zaretskii" To: Devrim Erdem Message-ID: <01c4c057$Blat.v2.2.2$c306b160@zahav.net.il> Content-Transfer-Encoding: 7BIT Content-Type: text/plain; charset=ISO-8859-1 CC: gdb@sources.redhat.com In-reply-to: (message from Devrim Erdem on Mon, 1 Nov 2004 12:03:58 +0100) Subject: Re: Attaching and inspecting crash with gdb Reply-to: Eli Zaretskii References: X-SW-Source: 2004-11/txt/msg00012.txt.bz2 > Date: Mon, 1 Nov 2004 12:03:58 +0100 > From: Devrim Erdem > > Classic problem. Customer uses software heavily. Software crashes from > time to time. No core dumps. Why ``no core dumps''? It's easier to cause them than to look for other solutions, in my experience. Then the customer could send you the core file, and you could debug the problem at your place.