Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: "Stephen A. Witt" <sawitt@electra.rsc.raytheon.com>
To: gdb@sources.redhat.com
Subject: GDB can't read core
Date: Wed, 26 Nov 2003 21:27:00 -0000	[thread overview]
Message-ID: <Pine.LNX.4.56.0311261310460.21580@zeus.rsc.raytheon.com> (raw)

I'm working on an IXP425-based system (actually right now the IXDP-425
board from Intel) and have built a cross-toolchain using Dan Kegel's
crosstool script. I've added a "cross" gdb (gdb-6.0) built to execute on
an i386 but with the target set to arm-unknown-linux-gnu. I'm trying to
get this gdb to look at a core file generated on my target board whan an
app segfaulted. I transferred the core file back to my development machine
and run gdb and tried to get it to read the core file. The following is
the error I get:

$ arm-unknown-linux-gnu-gdb -c ./core
GNU gdb 6.0
Copyright 2003 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you
are
welcome to change it and/or distribute copies of it under certain
conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB.  Type "show warranty" for
details.
This GDB was configured as "--host=i686-pc-linux-gnu
--target=arm-unknown-linux-gnu".
GDB can't read core files on this machine.
(gdb)


I've searched around and found some references to this problem, but never
did see a definitive answer (at least that I could understand). So, should
it be possible to debug core files in this way? Any tips on how to
proceed?

Thanks...


             reply	other threads:[~2003-11-26 21:27 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-26 21:27 Stephen A. Witt [this message]
2003-11-26 22:22 ` Paul Koning
2003-11-26 22:29   ` Daniel Jacobowitz
2003-11-26 22:34     ` Paul Koning
2003-11-26 22:37       ` Daniel Jacobowitz
2003-12-01 16:05         ` Andrew Cagney

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=Pine.LNX.4.56.0311261310460.21580@zeus.rsc.raytheon.com \
    --to=sawitt@electra.rsc.raytheon.com \
    --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