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 16:21:00 -0000 [thread overview]
Message-ID: <a6d8d9380805050921l64dec3acle8fb26c6115c36a3@mail.gmail.com> (raw)
In-Reply-To: <481F3008.5060200@redhat.com>
This version of insight was installed from Ubuntu repository. Maybe I
need to build one by myself:)))
Thanks for your help!
On Mon, May 5, 2008 at 12:04 PM, Keith Seitz <keiths@redhat.com> wrote:
> Kefei Lu wrote:
>
> > Thanks for the help! I've tried in console mode and the log file is
> > post as following. I'll also post this mail at gdb's mailing list.
> > Just feel strange why insight suddenly broke and why my gdb 6.6 is
> > still working. What I've done? :(
> >
>
> Two points. First, the session you posted is perfect. That is exactly what
> GDB folk are going to need to see. Second, You're using gdb 6.6, but you
> insight is based on 6.5 -- which is VERY old. At the very least, download
> and build the insight 6.6 tarball (or a newer one -- current release is
> 6.7.1). I'm not surprised to hear that a gdb of that vintage is having
> problems: there was a lot of churn in thread libraries and a bunch of gdb
> subsystems around that time.
>
> Keith
>
--
Sincerely,
Kefei Lu
------------------------
Kefei Lu, Ph.D. candidate
Dept. of Electrical and Computer Engineering
Univ. of Miami, U.S.A.
prev parent reply other threads:[~2008-05-05 16:21 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
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 [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=a6d8d9380805050921l64dec3acle8fb26c6115c36a3@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).