From: Adam Schuetze <adam@adam-schuetze.org>
To: Insight Mailing List <insight@sourceware.cygnus.com>
Subject: source window stops displaying executing code
Date: Fri, 03 Nov 2000 14:15:00 -0000 [thread overview]
Message-ID: <20001103141152.B1650@alpha.adam-schuetze.org> (raw)
Hi all,
I have come across an odd problem/wierdness with Insight. I am
using Insight 5.0, released May 2000. I have not tried any of
the snapshots, as I managed to get the original source to
compile (with some help from Fernando, thanks Fernando!).
I will try to explain what is going on in words; for
clarification (screen shots) you can go to
http://www.adam-schuetze.org/insight/insight_problem.htm
Ok. So I'm running a small program (I'm taking a c++ oo course,
beginner style). If I am stepping through line by line, and I
step off the end of the program, the source window blanks out,
and the dialog at the bottom says it is looking at
"libc-start.c", but the source code window is blank.
Perhaps of importance, when I place the cursor over the source
window, the cursor changes to a small "watch".
If I do another "n", the console display shows that my program
has exited properly, but the source file name window still says
it is looking at libc-start.c, even though it is blank.
If I do a "run" in the console window, the console window shows
that my program has restarted, and the "current variables"
window shows variables that I recognize as being in main() in my
program, but the current file name source code window is still
stuck on libc-start.c, even though it shows the program is now
in the function main(). So I can't see what is going on, as I
step through the program now.
If I try to change the "current file name" back to my program,
it gives me an error message:
Error: invalid command name
".srcwin().srcwin.container.pane1.childsite.con.p.pane4.childsite.st.lf.childsite.clipper.text"
I am unable to get myself out of this mess without exiting from
insight, and re-running it.
Am I overlooking something here? What is the "libc-start.c"
business about?
This is not fatal, but it is annoying :) Any help would be appreciated.
thanks,
--
Adam Schuetze <adam@adam-schuetze.org>
Get my pgp keys at http://www.adam-schuetze.org
next reply other threads:[~2000-11-03 14:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-03 14:15 Adam Schuetze [this message]
2000-11-03 15:21 ` Fernando Nasser
2000-11-03 16:01 ` Adam Schuetze
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=20001103141152.B1650@alpha.adam-schuetze.org \
--to=adam@adam-schuetze.org \
--cc=insight@sourceware.cygnus.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).