This is the mail archive of the
insight@sources.redhat.com
mailing list for the Insight project.
source window stops displaying executing code
- To: Insight Mailing List <insight at sourceware dot cygnus dot com>
- Subject: source window stops displaying executing code
- From: Adam Schuetze <adam at adam-schuetze dot org>
- Date: Fri, 3 Nov 2000 14:11:52 -0800
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