From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 30144 invoked by alias); 28 Jan 2003 03:51:56 -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 30129 invoked from network); 28 Jan 2003 03:51:54 -0000 Received: from unknown (HELO takamaka.act-europe.fr) (80.14.53.12) by 172.16.49.205 with SMTP; 28 Jan 2003 03:51:54 -0000 Received: by takamaka.act-europe.fr (Postfix, from userid 507) id 91ABFD34AE; Tue, 28 Jan 2003 07:51:47 +0400 (RET) Date: Tue, 28 Jan 2003 03:51:00 -0000 From: Joel Brobecker To: "Bennett F. Dill" Cc: gdb@sources.redhat.com Subject: Re: core while attached Message-ID: <20030128035147.GF6437@gnat.com> References: <20030127183252.GA9690@linux.dillfamily.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20030127183252.GA9690@linux.dillfamily.org> User-Agent: Mutt/1.4i X-SW-Source: 2003-01/txt/msg00452.txt.bz2 > Anyway, the application runs in the background and is a server to about > 25 clients concurrently. It takes a few hours for the app to sigsegv. > Now, it never dumped a core for some reason, so i just attach gdb to the > process and continue and wait for the error to rear its head. Maybe your server is larger than a certain size and that past this size the system elects not to dump a core file. I don't know on which system you are running, but you can usually raise the limit by using utilities like "ulimit", for instance "ulimit -c 100000" or somesuch. -- Joel