From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 8011 invoked by alias); 30 Apr 2009 19:08:37 -0000 Received: (qmail 8003 invoked by uid 22791); 30 Apr 2009 19:08:37 -0000 X-SWARE-Spam-Status: No, hits=-2.5 required=5.0 tests=AWL,BAYES_00 X-Spam-Check-By: sourceware.org Received: from mail3.caviumnetworks.com (HELO mail3.caviumnetworks.com) (12.108.191.235) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Thu, 30 Apr 2009 19:08:29 +0000 Received: from exch4.caveonetworks.com (Not Verified[192.168.16.23]) by mail3.caviumnetworks.com with MailMarshal (v6,2,2,3503) id ; Thu, 30 Apr 2009 15:08:07 -0400 Received: from exch4.caveonetworks.com ([192.168.16.23]) by exch4.caveonetworks.com with Microsoft SMTPSVC(6.0.3790.3959); Thu, 30 Apr 2009 12:08:03 -0700 Received: from dd1.caveonetworks.com ([64.169.86.201]) by exch4.caveonetworks.com with Microsoft SMTPSVC(6.0.3790.3959); Thu, 30 Apr 2009 12:08:03 -0700 Message-ID: <49F9F712.8060801@caviumnetworks.com> Date: Thu, 30 Apr 2009 19:11:00 -0000 From: David Daney User-Agent: Thunderbird 2.0.0.21 (X11/20090320) MIME-Version: 1.0 To: Eli Zaretskii CC: gdb@sourceware.org Subject: Re: Remote core file debugging References: <83k552dkw3.fsf@gnu.org> In-Reply-To: <83k552dkw3.fsf@gnu.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org X-SW-Source: 2009-04/txt/msg00237.txt.bz2 Eli Zaretskii wrote: > Is gdbserver supposed to support remote post-mortem debugging using a > core file on a remote machine? > > I have a situation where producing a backtrace from a dead program's > core file by running GDB on the machine where the application crashed > is impractical. This is because the program has huge amounts of debug > info, so starting GDB eats up all memory, which is a no-no, since the > application which restarted itself after a crash must be up at all > times, and eating up too much memory causes the OS to kill > applications. So I'm looking for ways of producing the equivalent of > "bt full", but without firing up GDB on the target system (a Red Hat > box). > > If gdbserver does not support this, what alternatives do I have? > I must be missing something, but why can't you move the core file to the debugging host and debug it there with gdb? David Daney