From: loody <miloody@gmail.com>
To: Keith Seitz <keiths@redhat.com>
Cc: Tom Tromey <tromey@redhat.com>, gdb@sourceware.org
Subject: Re: some questions about gdb
Date: Sun, 16 Jan 2011 13:47:00 -0000 [thread overview]
Message-ID: <AANLkTi=tVGOR24CHh6dwa=0epmTeL3uod_Dfxzfg2qCy@mail.gmail.com> (raw)
In-Reply-To: <4D2B7E74.1080206@redhat.com>
hi keith and Tom:
2011/1/11 Keith Seitz <keiths@redhat.com>:
> On 01/10/2011 12:58 PM, Tom Tromey wrote:
>>
>> You can't do this. You have to get a corresponding version of Insight.
>> I don't know whether a new version of Insight has been released.
>
> No, I haven't made a release since 6.8. Mostly because I didn't think no one
> else was using it. There have been enough requests, though, to warrant a
> release.
>
> I will release Insight shortly after the next GDB release. I am just
> fiddling with MinGW (which I hope to have "done" today-ish).
>
> But as it is, you can grab a CVS snapshot of src/gdb/gdbtk and src/libgui
> (and src/tcl, src/tk/, src/itcl if you need those) from the around the same
> date as the release you're interested in.
>
> If you want a 7.2 vintage Insight, CVS HEAD should work. Just drop in
> src/gdb/gdbtk and src/libgui, and you should be able to build Insight. This
> can be discussed on the insight@ mailing list if more details are needed.
I got the head version from insight CVS and it works with gdb 7.2.
But each time I press "n", gdb step as I press "si".
That means "n" should be like execute a line of c code, but on my gdb,
it execute an assembly line.
I config it as mipsel-linux.
Should I add more configs?
Thanks your help,
miloody
next prev parent reply other threads:[~2011-01-16 13:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-08 13:50 loody
2011-01-08 14:14 ` loody
2011-01-10 20:58 ` Tom Tromey
2011-01-10 21:47 ` Keith Seitz
2011-01-16 13:47 ` loody [this message]
2011-01-17 17:16 ` Tom Tromey
2011-01-16 19:03 ` Petr Hluzín
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='AANLkTi=tVGOR24CHh6dwa=0epmTeL3uod_Dfxzfg2qCy@mail.gmail.com' \
--to=miloody@gmail.com \
--cc=gdb@sourceware.org \
--cc=keiths@redhat.com \
--cc=tromey@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