From: "Kefei Lu" <lukefei@gmail.com>
To: "Keith Seitz" <keiths@redhat.com>, insight@sources.redhat.com
Subject: Re: [Problem] I can't do "next" in insight!
Date: Mon, 05 May 2008 14:37:00 -0000 [thread overview]
Message-ID: <a6d8d9380805050736p34674615q433a8781079664a6@mail.gmail.com> (raw)
In-Reply-To: <481E4FA4.7080304@redhat.com>
Hi Keith,
Thanks for reply.
Yes, my gdb works fine.
As I said, ``gdb --version'' and ``insight --version'' gives different
version number on gdb. So I guess insight wrapped its own version of
gdb, which might be broken.
But how can I invoke and test that version of gdb without invoking
insight to check the problem?
On Sun, May 4, 2008 at 8:07 PM, Keith Seitz <keiths@redhat.com> wrote:
> Kefei Lu wrote:
>
>
> > (gdb) n
> > Error: Warning:
> > Cannot insert breakpoint -11.
> > Error accessing memory address 0x29be0: Input/output error.
> >
>
> If gdb itself is not able to step the target, you're best bet is to bring
> this up on the gdb mailing list (gdb@). Insight is really just a GUI and a
> bunch of glue code to gdb. This is definitely a problem w/gdb proper, so you
> are likely to get much better information from the gdb community than I can
> offer.
>
> Keith
>
--
Sincerely,
Kefei Lu
------------------------
Kefei Lu, Ph.D. candidate
Dept. of Electrical and Computer Engineering
Univ. of Miami, U.S.A.
next prev parent reply other threads:[~2008-05-05 14:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-04 19:53 Kefei Lu
2008-05-05 0:14 ` Keith Seitz
2008-05-05 14:37 ` Kefei Lu [this message]
2008-05-05 15:49 ` Keith Seitz
2008-05-05 16:05 ` Kefei Lu
2008-05-05 16:09 ` Keith Seitz
[not found] ` <a6d8d9380805050904i3b8bf038if03de3187f43b38e@mail.gmail.com>
[not found] ` <481F3008.5060200@redhat.com>
2008-05-05 16:21 ` Kefei Lu
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=a6d8d9380805050736p34674615q433a8781079664a6@mail.gmail.com \
--to=lukefei@gmail.com \
--cc=insight@sources.redhat.com \
--cc=keiths@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).