From: Keith Seitz <keiths@redhat.com>
To: Raul Ito <itokoba@hotmail.com>
Cc: "insight@sources.redhat.com" <insight@sources.redhat.com>
Subject: Re: Insight Problem with SH3
Date: Wed, 03 Sep 2003 18:05:00 -0000 [thread overview]
Message-ID: <1062612440.2021.19.camel@lindt.uglyboxes.com> (raw)
In-Reply-To: <Law10-F28WQyASLiZy200012eff@hotmail.com>
On Sun, 2003-08-31 at 18:58, Raul Ito wrote:
> I have installed insight5.3 on my unix machine to use it for debugging the
> Hitachi SH3. At the RUN stage I got the GDB alert ,
>
> shared library handler failed to enable breakpoint
>
> Any suggestion about the cause of this problem? Do I have to build insight
> for SH mcu instead of using the native insight?
>
This problem most like occurs inside gdb. To be sure, though, you should
try using command-line gdb to debug your program. Please send output of
entire session, including the startup version message from gdb (so don't
use the "-q"/"--quiet" flags to start gdb).
Keith
prev parent reply other threads:[~2003-09-03 18:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-01 1:59 Raul Ito
2003-09-03 18:05 ` Keith Seitz [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=1062612440.2021.19.camel@lindt.uglyboxes.com \
--to=keiths@redhat.com \
--cc=insight@sources.redhat.com \
--cc=itokoba@hotmail.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).