This is the mail archive of the
insight@sources.redhat.com
mailing list for the Insight project.
Re: [Insight GUI] - Source codes not shown in source window
- To: Ting-Cheng Hsu <tc-hsu at ali dot com dot tw>
- Subject: Re: [Insight GUI] - Source codes not shown in source window
- From: Fernando Nasser <fnasser at redhat dot com>
- Date: Wed, 07 Mar 2001 07:52:19 -0500
- CC: insight at sourceware dot cygnus dot com
- Organization: Red Hat Canada
- References: <48256A08.0027D376.00@twalins2>
This has been fixed in more recent versions of Insight. You can get a
recent snapshot and it will find files under Windows correctly.
Fernando
Ting-Cheng Hsu wrote:
>
> Hello,
>
> Brief lists of environments:
> Cygwin1.dll : version 1.1.8
> Host OS : Windows 98
> Insight-5.0 : --target=mips64vr4300-elf (remote debugging)
>
> In console window, "list" command can correctly print source code.
> But the same source code is not shown in source window. I click
> and select the file name listed in the pull-down box at the lower
> left corner of source window, insight pops a window with an error message:
> couldn't stat "/home/hsutc/test/try.c": not such file or directory.
> The directory path and filename are correct, but insight just can't
> find it. There are two buttons in this popup window: "ok" and
> "stack trace". The following message is shown by clicking
> "stack trace" button:
>
> ---------------------------------------------------------------------
> couldn't stat "/home/hsutc/test/try.c": no such file or directory
> while executing
> "file mtime $f"
> (object "::.srcwin0.srcwin.container.pane1.childsite.con" method
> "::SrcTextWin::_mtime_changed" body line 7)
> invoked from within
> "_mtime_changed $filename"
> (object "::.srcwin0.srcwin.container.pane1.childsite.con" method
> "::SrcTextWin::FillSource" body line 10)
> invoked from within
> "FillSource t $tagname $filename $funcname $line $addr $pc_addr $lib"
> ("SOURCE" arm line 2)
> invoked from within
> "switch $current(mode) {
> SOURCE {
> FillSource t $tagname $filename $funcname $line $addr $pc_addr $lib
> }
> ASSEMBLY {
> FillAssembly..."
> (object "::.srcwin0.srcwin.container.pane1.childsite.con" method
> "::SrcTextWin::location" body line 26)
> invoked from within
> "$twin location $tag $name $funcname $line $addr $pc_addr $lib"
> (object "::.srcwin0.srcwin" method "::SrcWin::location" body line 52)
> invoked from within
> "location BROWSE_TAG [list $val "" $full 0 0 0 {}]"
> (object "::.srcwin0.srcwin" method "::SrcWin::_name" body line 22)
> invoked from within
> "::.srcwin0.srcwin _name .srcwin0.srcwin.container.pane3.childsite.con.name
> try.c"
> (in namespace inscope "::SrcWin" script line 1)
> invoked from within
> "namespace inscope ::SrcWin {::.srcwin0.srcwin _name}
> .srcwin0.srcwin.container.pane3.childsite.con.name try.c"
> ("after" script)errorCode is POSIX ENOENT {no such file or directory}
> ---------------------------------------------------------------------
>
> I don't know it's related to TCL/TK problems or to the underlying
> CYGWIN environments? I didn't find similar problems in insight's official
> problem report or the archives of this mail list (maybe it's because I
> did not find hard :> ). Thanks for any kinds of help.
>
> Regards,
> TC Hsu
> Acer Laboratories, Inc.
--
Fernando Nasser
Red Hat Canada Ltd. E-Mail: fnasser@redhat.com
2323 Yonge Street, Suite #300
Toronto, Ontario M4P 2C9