Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: "Paul J.Y. Lahaie" <pjlahaie@steamballoon.com>
To: gdb@sources.redhat.com
Subject: Problem cross-debugging from Solaris to Linux/PPC
Date: Fri, 04 Oct 2002 09:46:00 -0000	[thread overview]
Message-ID: <1033750049.3667.19.camel@elenuial.steamballoon.com> (raw)

I'm trying to cross-debug from Solaris 9/SPARC to Linux/PPC and I am
unable to get it working.

I've got Linux/x86 to Linux/PPC working with gdb 5.2 and I am using the
same gdbserver on the Linux/PPC host.

On the Solaris host I get the following:

(gdb) file ~/hello
Reading symbols from ~/hello...done.
(gdb) target remote ppc:5000
Remote debugging using ppc:5000
0x30010e40 in ?? ()
(gdb) break main
Breakpoint 1 at 0x100004bc: file hello.c, line 5.
(gdb) cont
Continuing.
warning: Cannot insert breakpoint -1:
Cannot access memory at address 0x3001a084
(gdb)


I've tried both 5.2 and 5.2.1, compiled with gcc 3.2 and gcc 2.95.3.

Paul


             reply	other threads:[~2002-10-04 16:46 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-04  9:46 Paul J.Y. Lahaie [this message]
2002-10-04 11:39 ` Paul Koning

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=1033750049.3667.19.camel@elenuial.steamballoon.com \
    --to=pjlahaie@steamballoon.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