Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Michael Snyder <msnyder@vmware.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: David Daney <ddaney@caviumnetworks.com>,
	  "gdb@sourceware.org" <gdb@sourceware.org>
Subject: Re: Remote core file debugging
Date: Thu, 30 Apr 2009 19:40:00 -0000	[thread overview]
Message-ID: <49F9FABF.6040108@vmware.com> (raw)
In-Reply-To: <83hc06djug.fsf@gnu.org>

Eli Zaretskii wrote:
>> Date: Thu, 30 Apr 2009 12:08:02 -0700
>> From: David Daney <ddaney@caviumnetworks.com>
>> 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.  It'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.  Your server would
only need to understand a reasonably small subset of commands
(memory read, register read, possibly threads if your system
includes them).


  reply	other threads:[~2009-04-30 19:31 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-30 19:08 Eli Zaretskii
2009-04-30 19:11 ` David Daney
2009-04-30 19:28   ` Eli Zaretskii
2009-04-30 19:40     ` Michael Snyder [this message]
2009-05-04  0:29       ` Hui Zhu
2009-04-30 19:26 ` Daniel Jacobowitz
2009-04-30 19:31   ` Eli Zaretskii
2009-04-30 21:45 ` Mark Kettenis
2009-05-01  8:06   ` Eli Zaretskii

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=49F9FABF.6040108@vmware.com \
    --to=msnyder@vmware.com \
    --cc=ddaney@caviumnetworks.com \
    --cc=eliz@gnu.org \
    --cc=gdb@sourceware.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox