From: Paul Koning <pkoning@equallogic.com>
To: pjlahaie@steamballoon.com
Cc: gdb@sources.redhat.com
Subject: Re: Problem cross-debugging from Solaris to Linux/PPC
Date: Fri, 04 Oct 2002 11:39:00 -0000 [thread overview]
Message-ID: <15773.57464.541988.125069@pkoning.dev.equallogic.com> (raw)
In-Reply-To: <1033750049.3667.19.camel@elenuial.steamballoon.com>
>>>>> "Paul" == Paul J Y Lahaie <Paul> writes:
Paul> I'm trying to cross-debug from Solaris 9/SPARC to Linux/PPC and
Paul> I am unable to get it working.
Paul> I've got Linux/x86 to Linux/PPC working with gdb 5.2 and I am
Paul> using the same gdbserver on the Linux/PPC host.
Paul> On the Solaris host I get the following:
Paul> (gdb) file ~/hello Reading symbols from ~/hello...done. (gdb)
Paul> target remote ppc:5000 Remote debugging using ppc:5000
Paul> 0x30010e40 in ?? () (gdb) break main Breakpoint 1 at
Paul> 0x100004bc: file hello.c, line 5. (gdb) cont Continuing.
Paul> warning: Cannot insert breakpoint -1: Cannot access memory at
Paul> address 0x3001a084 (gdb)
I tripped over this too on a different target. What a pain.
The problem is that gdb is trying to set a breakpoint at _start,
__start, or main, whichever it finds first. If the one it finds is an
address that you can't access, you get this error.
It sure would be better if gdb would ignore errors in such attempts to
set internally generated magical breakpoints, rather than throwing up
like this.
As a solution, either make _start or __start go away (so main is used,
which apparently is a valid address) or redefine them to some innocent
address.
paul
prev parent reply other threads:[~2002-10-04 18:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-04 9:46 Paul J.Y. Lahaie
2002-10-04 11:39 ` Paul Koning [this message]
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=15773.57464.541988.125069@pkoning.dev.equallogic.com \
--to=pkoning@equallogic.com \
--cc=gdb@sources.redhat.com \
--cc=pjlahaie@steamballoon.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