From: Keith Seitz <keiths@redhat.com>
To: Bahadir Balban <bbalban@b-labs.com>
Cc: insight@sourceware.org
Subject: Re: Next Release Status
Date: Mon, 19 Dec 2011 17:41:00 -0000 [thread overview]
Message-ID: <4EEF7732.4030501@redhat.com> (raw)
In-Reply-To: <1324233443.4090.11.camel@bbalban-desktop>
On 12/18/2011 10:37 AM, Bahadir Balban wrote:
> 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?
I just built CVS HEAD to do some testing and build-fixing. I am not
seeing this.
If you open a console window and enter, "tk gdb_loc" after you step your
inferior, what does it say? This is essentially the function that the
GUI uses to update its location information from the inferior's state.
You can also open a debug window to see any warning/errors by entering
"tk ManagedWin::open DebugWin". As you step through your inferior, it
will update with any messages. [Alternative, set GDBTK_DEBUG=1 in your
environment before running insight. That will output the debug messages
to the file "insight.log".]
> Is there a known stable cvs branch? (I could not locate the git repo).
CVS HEAD is all there is. Insight is unfortunately not in GIT yet.
Keith
next prev parent reply other threads:[~2011-12-19 17:41 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
2011-12-19 17:41 ` Keith Seitz [this message]
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=4EEF7732.4030501@redhat.com \
--to=keiths@redhat.com \
--cc=bbalban@b-labs.com \
--cc=insight@sourceware.org \
/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).