From: Bahadir Balban <bbalban@b-labs.com>
To: Keith Seitz <keiths@redhat.com>
Cc: insight@sourceware.org, Dawid Ciezarkiewicz <dawidc@b-labs.com>
Subject: Re: Next Release Status
Date: Sun, 18 Dec 2011 18:37:00 -0000 [thread overview]
Message-ID: <1324233443.4090.11.camel@bbalban-desktop> (raw)
In-Reply-To: <4EECDC95.8010803@redhat.com>
On Sat, 2011-12-17 at 10:16 -0800, Keith Seitz wrote:
> No. Insight *is* gdb. That's what makes it so much faster than Eclipse,
> emacs, DDD, etc, all of which have to process MI. Insight is the same
> executable.
OK, thanks for the info.
>
> Just checkout the latest sources and build. Like I mentioned in my other
> email, I've been doing this for years.
>
> That reminds me, I believe I have a patch to commit... O:-)
>
> Keith
I built and installed the latest CVS (insight version 7.4-cvs). However
when I load an executable and step, the execution moves forward, but the
source screen does not update; it's in the very first state (with the
green bar stuck at the first line of source). Anyone experienced this
behavior?
Is there a known stable cvs branch? (I could not locate the git repo).
Thanks,
Bahadir
next prev parent reply other threads:[~2011-12-18 18:37 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-15 14:22 Bahadir Balban
2011-12-15 14:38 ` Bahadir Balban
2011-12-17 18:17 ` Keith Seitz
2011-12-18 18:37 ` Bahadir Balban [this message]
2011-12-19 17:41 ` Keith Seitz
2011-12-20 12:18 ` Bahadir Balban
2011-12-17 18:14 ` Keith Seitz
-- strict thread matches above, loose matches on Subject: below --
2011-11-08 17:51 Keith Seitz
2011-11-08 22:14 ` Matthias Andree
2011-11-09 0:17 ` Christopher Faylor
2011-11-09 23:32 ` Keith Seitz
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=1324233443.4090.11.camel@bbalban-desktop \
--to=bbalban@b-labs.com \
--cc=dawidc@b-labs.com \
--cc=insight@sourceware.org \
--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).