Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: "Joe Goh" <joe@willowglen.com.sg>
To: gdb@sources.redhat.com
Subject: Examining mips-openbsd core files from i386-openbsd host
Date: Thu, 24 Feb 2005 17:11:00 -0000	[thread overview]
Message-ID: <opsmov93cvrcgt5a@joe-pc> (raw)

Hi everyone,

I'm having trouble compiling gdb 6.3 to be able to examine core files from  
a mipsel-openbsd host, using an i386-openbsd host.

I'm compiling gdb on an OpenBSD 3.6 i386 host with --target=mipsel-openbsd  
and the build succeeds, but when I try to open a core file, gdb complains  
of, "GDB can't read core files on this machine.".

Printing out some debug messages from find_core_target() in gdb/target.c  
reveals that there are none of the "target_ops" structures in  
"target_structs" are "core_stratum"'s.

Are there any switches I need to pass to "configure" to be able to do  
cross architecture core file examination?  Or are there some settings that  
I need to do in runtime from the gdb prompt?

Thanks in advance!
Joe


                 reply	other threads:[~2005-02-24  6:54 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=opsmov93cvrcgt5a@joe-pc \
    --to=joe@willowglen.com.sg \
    --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