Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Aaron Gaudio <agaudio@eng.mc.xerox.com>
To: gdb@sources.redhat.com
Subject: Trying to debug an x86 core on a Sparc
Date: Thu, 09 Jun 2005 19:19:00 -0000	[thread overview]
Message-ID: <1118344705.27729.7.camel@rockhopper> (raw)

[-- Attachment #1: Type: text/plain, Size: 1127 bytes --]

Hello all,

I've got gdb built using the configure arg '--target i386-pc-
solaris2.10', on build host 'sparc-sun-solaris2.8'. I'm trying to debug
a core file which was produced on an x86 Solaris 10 box. I do have a
copy of the x86 executable available on the sparc box.

I try to load the executable and core using i386-pc-solaris2.10-gdb core
executable

The executable has a bunch of dll dependencies, with paths like
"/usr/lib/libsomething.so.1". These are fine on the x86 box, but on the
Sparc box, obviously "/usr/lib/libsomething.so.1" is a sparc binary and
not compatible. The x86 library is in a different directory (call
it /opt/i386-pc-solaris2.10-sysroot). I want to tell gdb to look at the
sysroot directory and not the absolute rpath specified in the
executable. Is there any way to do this?


-- 
Aaron Gaudio           agaudio @ eng.mc.xerox.com           585-422-6876

                  While life is yours, live joyously;
                None can escape Death's searching eye:
                When once this frame of ours they burn,
                   How shall it e'er again return?

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 197 bytes --]

             reply	other threads:[~2005-06-09 19:19 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-09 19:19 Aaron Gaudio [this message]
2005-06-09 19:47 ` Daniel Jacobowitz
2005-06-09 20:57   ` Aaron Gaudio
2005-06-09 21:10     ` Daniel Jacobowitz
2005-06-10 15:10       ` Aaron Gaudio
2005-06-12  8:03 ` Mark Kettenis

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=1118344705.27729.7.camel@rockhopper \
    --to=agaudio@eng.mc.xerox.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