Re: [Mingw-users] Proposed: Insight/gdb

[Dave M. <win...@nt...>]

Wells, Roger K. wrote:
> Thanks for the reply.  I will put together a minimal case but while I am
> doing that there may be another clue.  One of my colleagues has used the
> same release successfully (in fact he merely copied my installation).  When
> I first used it I got messages about not finding itcl.tcl, etc.  I then set
> the following environment variables:
>   
That would probably point to an environment issue somewhere. Perhaps 
your installation is picking up previously installed Tcl/Tk components 
rather than those supplied with Insight. I'm a bit confused about this 
though since I was under the impression that dlls in the same directory 
as the executable took preference over those in the path.

> ITCL_LIBRARY=d:\"Program Files"\insight\share\itcl3.2
> ITK_LIBRARY=d:\"Program Files"\insight\share\itk3.2
> TCL_LIBRARY=d:\"Program Files"\insight\share\tcl8.4
> TK_LIBRARY=d:\"Program Files"\insight\share\tk8.4
>   
It might be worth moving this to a path without spaces, I've had endless 
trouble with gnu tools and spaces so I just don't do it. It's probably 
also worth looking for any Insight/tcl/tk environment variables that may 
be referring to another installation, possibly including the 
tclConfig.sh and tkConfig.sh files found in the Insight lib directory. 
The config files have absolute paths which relate to my build and 
install environment though I've moved the installed files around drives 
and paths with no problems here.

> Now the insight GUI comes up but fails when I attempt to step into main().
> My colleague who experienced a successful use of insight did not get
> prompted about itcl.tcl, set none of the above environment variable, and
> debugged his application in the expected way.
>
> Does this mean that his invocation of insight is resolving references to
> Tcl/Tk resources fortuitously via previous installed applications that also
> installed Tcl/Tk somewhere on his machine?
>   
I think it may mean that his Insight is using the tcl/tk components 
provided rather than any other version and yours is being broken by 
previous installs and/or environment variables.

Getting Insight to work involved a SEH related patch to Tcl to allow 
setjmp to work properly - see the thread at 
http://sources.redhat.com/ml/insight/2005-q3/msg00052.html for details. 
(note: the patch in the first message is the wrong one, it's corrected a 
few messages in)
> We have developed a number of Tcl/Tk applications and those of us in the
> development community could easily have wildly different environments with
> regard to Tcl/Tk installations.  In fact one of our challenges has been
> ensuring that our stuff runs regardless of what Tcl/Tk components are
> installed on the host.
>
> Thanks again and I will get together a minimal example.
>   

I think we've possible excluded the possibility that Insight doesn't 
understand the debug info output by your build. You could check that 
binaries built on your machine are debuggable with your colleagues 
installation.


Dave