From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 5733 invoked by alias); 30 Apr 2009 21:37:21 -0000 Received: (qmail 5724 invoked by uid 22791); 30 Apr 2009 21:37:20 -0000 X-SWARE-Spam-Status: No, hits=-2.5 required=5.0 tests=AWL,BAYES_00 X-Spam-Check-By: sourceware.org Received: from sibelius.xs4all.nl (HELO sibelius.xs4all.nl) (82.92.89.47) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Thu, 30 Apr 2009 21:37:15 +0000 Received: from brahms.sibelius.xs4all.nl (kettenis@localhost [127.0.0.1]) by brahms.sibelius.xs4all.nl (8.14.3/8.14.3) with ESMTP id n3ULb5an006611; Thu, 30 Apr 2009 23:37:06 +0200 (CEST) Received: (from kettenis@localhost) by brahms.sibelius.xs4all.nl (8.14.3/8.14.3/Submit) id n3ULb5eM004677; Thu, 30 Apr 2009 23:37:05 +0200 (CEST) Date: Thu, 30 Apr 2009 21:45:00 -0000 Message-Id: <200904302137.n3ULb5eM004677@brahms.sibelius.xs4all.nl> From: Mark Kettenis To: eliz@gnu.org CC: gdb@sourceware.org In-reply-to: <83k552dkw3.fsf@gnu.org> (message from Eli Zaretskii on Thu, 30 Apr 2009 22:03:24 +0300) Subject: Re: Remote core file debugging References: <83k552dkw3.fsf@gnu.org> 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/msg00246.txt.bz2 > Date: Thu, 30 Apr 2009 22:03:24 +0300 > From: Eli Zaretskii > > Is gdbserver supposed to support remote post-mortem debugging using a > core file on a remote machine? I don't think it is. > 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? Copy the core file and binaries to a somewhat more powerful machine and use a cross-gdb (the same you'd probably use with gdbserver)?