From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 21349 invoked by alias); 4 May 2009 00:29:12 -0000 Received: (qmail 21341 invoked by uid 22791); 4 May 2009 00:29:11 -0000 X-SWARE-Spam-Status: No, hits=-1.6 required=5.0 tests=AWL,BAYES_00,SARE_MSGID_LONG40,SPF_PASS X-Spam-Check-By: sourceware.org Received: from ti-out-0910.google.com (HELO ti-out-0910.google.com) (209.85.142.187) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Mon, 04 May 2009 00:29:06 +0000 Received: by ti-out-0910.google.com with SMTP id a1so316719tib.12 for ; Sun, 03 May 2009 17:29:03 -0700 (PDT) MIME-Version: 1.0 Received: by 10.110.16.15 with SMTP id 15mr385237tip.53.1241396943547; Sun, 03 May 2009 17:29:03 -0700 (PDT) In-Reply-To: <49F9FABF.6040108@vmware.com> References: <83k552dkw3.fsf@gnu.org> <49F9F712.8060801@caviumnetworks.com> <83hc06djug.fsf@gnu.org> <49F9FABF.6040108@vmware.com> Date: Mon, 04 May 2009 00:29:00 -0000 Message-ID: Subject: Re: Remote core file debugging From: Hui Zhu To: Michael Snyder Cc: Eli Zaretskii , David Daney , "gdb@sourceware.org" Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable 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-05/txt/msg00012.txt.bz2 On Fri, May 1, 2009 at 03:23, Michael Snyder wrote: > Eli Zaretskii wrote: >>> >>> Date: Thu, 30 Apr 2009 12:08:02 -0700 >>> From: David Daney >>> CC: gdb@sourceware.org >>> >>> I must be missing something, but why can't you move the core file to the >>> debugging host and debug it there with gdb? >> >> Sorry, I should have said that in the first place: because it's huge, >> and there are quite a few of them. =A0It's not a single target system, >> either: there are a few dozen of them, so copying huge core files from >> all of them would be at least time consuming if not impractical. > > GDBserver cannot currently do what you want. > > Options include > 1) Teach gdbserver to understand core files, and > 2) Write a corefile server that understands gdb serial protocol. > > #2 might be a bit easier, at least if you start with libbfd > which already knows how to read core files. =A0Your server would > only need to understand a reasonably small subset of commands > (memory read, register read, possibly threads if your system > includes them). #2 sounds cool. Maybe it can be optional function of gdbserver.