public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Grant Edwards <grante@visi.com>
To: eCos Disuss <ecos-discuss@sourceware.cygnus.com>
Subject: Re: [ECOS] gdb and binary core files
Date: Wed, 22 Aug 2001 08:43:00 -0000	[thread overview]
Message-ID: <20010822104538.A31674@visi.com> (raw)
In-Reply-To: <20010822103030.B5690@biferten.ma.tech.ascom.ch>

On Wed, Aug 22, 2001 at 10:30:30AM +0200, Andrew Lunn wrote:

> Im trying to do something along the lines of a core dump for eCos. I
> just want something realy simple. In my setup its easy for me to get a
> complete copy of the DRAM contents onto my host system. I then have to
> get gdb to use this data. By default arm-elf-gdb does not seem to
> support core files. Not a good start. Also, it does not seem possible
> to specify the format of the core file. You can use "set gnutarget" to
> set the BFD format, but that seems to apply to everything. I want gdb
> to use elf for my executable, and binary for my core file.

Sometime within the past couple years, somebody posted a patch
to the gdb mailing list that allowed you to dump a region of
memory to file (I don't remember the format, but I think it was
something understood by objcopy).

> Does anyone have any ideas or pointers?

It sure would be handy if gdb could dump chunks of memory to
disk.  Over the past couple years I've spent hours cutting and
pasting between xterms in order to run chunks of target memory
through post-mortem tools.

I'm sure it would have taken all of about half a day to add a
"dump-region" command to gdb and do it right.  One of these
days...

-- 
Grant Edwards
grante@visi.com

  reply	other threads:[~2001-08-22  8:43 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-08-22  1:30 Andrew Lunn
2001-08-22  8:43 ` Grant Edwards [this message]
2001-08-22  8:45   ` Grant Edwards

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=20010822104538.A31674@visi.com \
    --to=grante@visi.com \
    --cc=ecos-discuss@sourceware.cygnus.com \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).