From: Paul Koning <pkoning@equallogic.com>
To: drow@false.org
Cc: Cenedese@indel.ch, gdb@sources.redhat.com
Subject: Re: core file not loaded
Date: Wed, 06 Oct 2004 17:45:00 -0000 [thread overview]
Message-ID: <16740.11872.402907.34596@gargle.gargle.HOWL> (raw)
In-Reply-To: <20041006171222.GA7809@nevyn.them.org>
>>>>> "Daniel" == Daniel Jacobowitz <drow@false.org> writes:
Daniel> On Wed, Oct 06, 2004 at 04:16:08PM +0200, Fabian Cenedese
Daniel> wrote:
>> >> gdb-6.1.1 on cygwin, target=PPC
>> >
>> >More specific - what target triplet?
>>
>> Sorry, --host=i686-pc-cygwin --target=powerpc-eabi
>> ...
>> My understanding was, that I could take a memory snapshot of the
>> target (in this case about 4MB) and feed this to gdb so gdb will
>> use this file for read accesses instead of reading a physical
>> target (in addition to the symbolfile). Is this wrong? Or is this
>> not a core file?
Daniel> That's not a core file. You can probably convert it to a
Daniel> core file, but you'd also have to teach the BFD and GDB
Daniel> powerpc-eabi support to recognize it as a powerpc-eabi core
Daniel> file.
Daniel> A core file is one of several "standard" formats, generated
Daniel> by various operating systems - lately, a particular kind of
Daniel> ELF object. Easiest might be to convert your binary dump to
Daniel> an ELF core file and copy support from powerpc-linux.
Daniel> Note that a memory dump isn't enough; for instance, you've
Daniel> lost all register values.
The other issue (at least when last I looked) is that gdb is only
willing to handle corefiles for native builds, not for crossbuilds.
If your target state is more than just a single executing program,
you're really dealing with a kernel corefile, which is a whole
different class of beast.
paul
next prev parent reply other threads:[~2004-10-06 17:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-06 11:50 Fabian Cenedese
2004-10-06 14:06 ` Daniel Jacobowitz
2004-10-06 16:22 ` Fabian Cenedese
2004-10-06 17:12 ` Daniel Jacobowitz
2004-10-06 17:45 ` Paul Koning [this message]
2004-10-06 17:45 ` Kris Warkentin
2004-10-06 17:55 ` Daniel Jacobowitz
2004-10-06 17:41 Xinan Tang
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=16740.11872.402907.34596@gargle.gargle.HOWL \
--to=pkoning@equallogic.com \
--cc=Cenedese@indel.ch \
--cc=drow@false.org \
--cc=gdb@sources.redhat.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).