Insight port to the 'original' Windows

Keith Seitz keiths@cygnus.com
Fri May 4 07:05:00 GMT 2001


On Thu, 4 May 2000, Kai Ruottu wrote:

> The result is attached as an screenshot showing the problem....

You ARE adventurous, aren't you? :-)

>  Has someone to give a clue what could cause this?  Is there some
> fundamental feature (threads etc.) taken into work into the Insight
> scripts etc. in 1999 causing this?  Ok, as seen in the source window,
> all the stuff in the lower part has not been drawn....

For some reason, the srctextwin has not drawn itself. It could be a bug in
Insight or a bug in Tcl. I would start Insight withe environment varialble
GDBTK_DEBUG set (to two) in your environment. Of course, I don't know if
such a thing exists on the original version of windows, so you may have to
edit your gdbtk.ini. There is a section labeled "windows" with the
property "active={list of windows to open when started". Add "DebugWin".
This will automatically bring up the DebugWindow when you start Insight.
Maybe that will provide some insight into your problem. (Ok, I couildn't
resist that one. :-)

>  The scripts etc. taken from the GNUPro-98r2 sources (those from
> Hitachi) work quite well under Win32s, but the GUI from that time
> is a little 'clumsy', so I would like to upgrade the base in the
> Mingw/Win3.1x hosted Insights.... And after this to put the diffs
> somewhere (also for the working Mingw/Win32 one...)

Unfortunately, a whole lot has changed since then. There is almost no way
of knowing what broke it.

Let us know if the DebugWin shows any errors...
Keith




More information about the Insight mailing list