From: Daniel Jacobowitz <drow@false.org>
To: Arun Biyani <abiyani@unix.telasic.com>
Cc: gdb@sourceware.org
Subject: Re: Setting library path
Date: Mon, 08 Jan 2007 19:16:00 -0000 [thread overview]
Message-ID: <20070108191605.GA22240@nevyn.them.org> (raw)
In-Reply-To: <45A295B3.6010504@unix.telasic.com>
On Mon, Jan 08, 2007 at 11:04:19AM -0800, Arun Biyani wrote:
> I have been trying to setup GDB for cross debugging. Host x86 Linux.
> Remote Coldfire 5272. Gdb behaves
> strangely. Setting a breakpoint causes illegal instruction trap after
> the breakpoint is executed. While searching
> the web, I came across this hint below.
> How do I tell gdb where the libraries are? I am using "m68k-elf-gdb"
> which I found at snapgear.org. On the
> system, I can see /usr/local/m68k-uclinux/lib
That is for targeting a system using shared libraries. If you are
using m68k-elf, you are probably not using shared libraries, and this
won't help you.
I don't know what might be wrong, but it sounds like your GDB and
target do not agree on the proper breakpoint.
--
Daniel Jacobowitz
CodeSourcery
prev parent reply other threads:[~2007-01-08 19:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-08 19:04 Arun Biyani
2007-01-08 19:16 ` Daniel Jacobowitz [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=20070108191605.GA22240@nevyn.them.org \
--to=drow@false.org \
--cc=abiyani@unix.telasic.com \
--cc=gdb@sourceware.org \
/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