Re: Hi,

Re: Hi,

[Ken Moore]

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 461 bytes --]

win98 for building and running,  m68k-elf 
target:
 
I got the newest fileset from the ftp site, and did the 
configure, make, make install process.  At the end I had a version that 
launched the gui  :)
 
I have noticed that insight crashes if you load a command file 
"source filename" with more than one line of "set" like the following "set 
*(short*)0xfffa46 = 0x03fd".   This is probably a gdb error, so I will 
post it on that list.

Please do not post to the insight list in HTML!

[Mo DeJong]

The subject says it all. Please do not use an email client
that send email in HTML. Lots of people will be unable to
read your email.

Mo DeJong
Red Hat Inc

Re: Hi,

[Ken Moore]

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 2512 bytes --]

I did the install a week ago from the cygnus site.  The win98 "start 
menu" shows it as cygwin 1.1.0, but the downloaded tar.gz file shows it as 
1.1.2.
 
I did "make install" from the insight directory. This ran to 
completion and put many files (and sub dirs) into the "cygwin\usr\local\share" 
directory.  gdb.exe itself is not moved anywhere.
 
The gdb.exe wants the previously listed cyg*.dll files to run.  I had 
to manually locate these and copy them to a directory with gdb.exe. This didnt 
seem like a great thing to have to do, but it allowed the exe to run, 
otherwise it popped up a message box saying it could not find xxxx.dll.
 
Thanks,
Ken
 
 
—----------------------------------------------------------------------------
Hi,

What version of cygwin are you using?  (from where did you get,
what is the snapshot date etc.)

Have you tried "make install" and to use the so installed version?


-- 
Fernando Nasser
Red Hat Canada Ltd.                     E-Mail:  fnasser@cygnus.com
2323 Yonge Street, Suite #300           Tel:  416-482-2661 ext. 311
Toronto, Ontario   M4P 2C9              Fax:  416-482-6299

 
—----------------------------------------------------------------------------

Hi,
 
Cant get the GUI for insight to run.
 
I downloaded the Insight 5.0 release and was finally able to build it (new 
to this stuff).  When trying to run "gdb.exe" it briefly opens then closes 
a dos window, the GUI never runs.  If I run with the "--nw" option, then 
the command line version opens up normally.
 
I ran gdb within gdb and got the following output.
(gdb) run Starting program: 
c:\gnu\insight-5.0\m68k-elf\gdb.exe 66600000:C:/GNU/INSIGHT-5.0/M68K-ELF/TIX4180.DLL 7fcb0000:C:/WINDOWS/SYSTEM/SHELL32.DLL bfe90000:C:/WINDOWS/SYSTEM/COMCTL32.DLL 70bd0000:C:/WINDOWS/SYSTEM/SHLWAPI.DLL 7fe10000:C:/WINDOWS/SYSTEM/COMDLG32.DLL 66300000:C:/GNU/INSIGHT-5.0/M68K-ELF/CYGTK80.DLL 66800000:C:/GNU/INSIGHT-5.0/M68K-ELF/CYGITK30.DLL bfe80000:C:/WINDOWS/SYSTEM/ADVAPI32.DLL bff20000:C:/WINDOWS/SYSTEM/GDI32.DLL bff50000:C:/WINDOWS/SYSTEM/USER32.DLL bff70000:C:/WINDOWS/SYSTEM/KERNEL32.DLL 61000000:C:/GNU/INSIGHT-5.0/M68K-ELF/CYGWIN1.DLL 66000000:C:/GNU/INSIGHT-5.0/M68K-ELF/CYGTCL80.DLL 66700000:C:/GNU/INSIGHT-5.0/M68K-ELF/CYGITCL30.DLL
 
Program exited normally. (gdb)
Any ideas on why the GUI is not running?
 
Running and compiling on Win98.   --host=i586-pc-cygwin  
--target=m68k-elf
 
Thanks,
Kenneth Moore

Re: Hi,

[Fernando Nasser]

(I don't know why I can't quote your original messages... HTML?)


Anyways, here it is:

 I did the install a week ago from the cygnus site.  The win98 "start menu" shows
 it as cygwin 1.1.0, but the downloaded tar.gz file shows it as 1.1.2.
  
Humm, this may have been an oversight. I will tell Cygwin people about it.
It doesn't hurt a thing though.

 I did "make install" from the insight directory. This ran to completion and put
 many files (and sub dirs) into the "cygwin\usr\local\share" directory.  gdb.exe
 itself is not moved anywhere.
  
Ken, you must go through the building instructions and the manual again.
A cross gdb will have an installed name that reflects the target platform.
The installed gdb will be m68k-elf-gdb.  Try it.  But before you do, look at
the following item.


 The gdb.exe wants the previously listed cyg*.dll files to run.  I had to manually
 locate these and copy them to a directory with gdb.exe. This didnt seem like a
 great thing to have to do, but it allowed the exe to run, otherwise it popped up a
 message box saying it could not find xxxx.dll.

This way you make absolutely certain thins will go wrong.  You must ensure, by all
means, that you don't have two copies of the DLL anywhere in your system.  And please 
note that they can be found in so many forms that the best way to ensure things
won't go wrong is having exactly one copy in your system (renaming to xxxx_dll, with
the underscore character also works.  adding things after the dll do not; deleting
the copies is safer).

Use the Find Windows utility to get rid of duplicates.

Use the "cygcheck -s" command to be sure the right ones are being picked.
If you need more help and post again, include that output as it may help.

But before posting, please, take a second look at the documentation: cygwin
and gdb.

Good luck!



-- 
Fernando Nasser
Red Hat Canada Ltd.                     E-Mail:  fnasser@cygnus.com

Re: Hi,

[Chris Faylor]

On Wed, Jun 21, 2000 at 11:06:50AM -0400, Ken Moore wrote:
>I did the install a week ago from the cygnus site.  The win98 "start
>menu" shows it as cygwin 1.1.0, but the downloaded tar.gz file shows it
>as 1.1.2.
>
>I did "make install" from the insight directory.  This ran to
>completion and put many files (and sub dirs) into the
>"cygwin\usr\local\share" directory.  gdb.exe itself is not moved
>anywhere.
>
>The gdb.exe wants the previously listed cyg*.dll files to run.  I had
>to manually locate these and copy them to a directory with gdb.exe.
>This didnt seem like a great thing to have to do, but it allowed the
>exe to run, otherwise it popped up a message box saying it could not
>find xxxx.dll.

Some path handling changed in Cygwin a couple of months ago that caused
problems for the tcl code in insight.  They caused insight to be unable
to find some of the startup files that it needs.

The problems have been rectified in the insight CVS sources and in the
insight snapshots.  Your best bet is to use those rather than the official
5.0 release.

I don't believe that the 5.0 release works well on W2K either, if that is
an issue.  The snapshots and CVS sources should work fine.

cgf

Hi,

[Ken Moore]

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1258 bytes --]

Hi,
 
Cant get the GUI for insight to run.
 
I downloaded the Insight 5.0 release and was finally able to build it (new 
to this stuff).  When trying to run "gdb.exe" it briefly opens then closes 
a dos window, the GUI never runs.  If I run with the "--nw" option, then 
the command line version opens up normally.
 
I ran gdb within gdb and got the following output.
(gdb) run Starting program: 
c:\gnu\insight-5.0\m68k-elf\gdb.exe 66600000:C:/GNU/INSIGHT-5.0/M68K-ELF/TIX4180.DLL 7fcb0000:C:/WINDOWS/SYSTEM/SHELL32.DLL bfe90000:C:/WINDOWS/SYSTEM/COMCTL32.DLL 70bd0000:C:/WINDOWS/SYSTEM/SHLWAPI.DLL 7fe10000:C:/WINDOWS/SYSTEM/COMDLG32.DLL 66300000:C:/GNU/INSIGHT-5.0/M68K-ELF/CYGTK80.DLL 66800000:C:/GNU/INSIGHT-5.0/M68K-ELF/CYGITK30.DLL bfe80000:C:/WINDOWS/SYSTEM/ADVAPI32.DLL bff20000:C:/WINDOWS/SYSTEM/GDI32.DLL bff50000:C:/WINDOWS/SYSTEM/USER32.DLL bff70000:C:/WINDOWS/SYSTEM/KERNEL32.DLL 61000000:C:/GNU/INSIGHT-5.0/M68K-ELF/CYGWIN1.DLL 66000000:C:/GNU/INSIGHT-5.0/M68K-ELF/CYGTCL80.DLL 66700000:C:/GNU/INSIGHT-5.0/M68K-ELF/CYGITCL30.DLL
 
Program exited normally. (gdb)
Any ideas on why the GUI is not running?
 
Running and compiling on Win98.   --host=i586-pc-cygwin  
--target=m68k-elf
 
Thanks,
Kenneth Moore
 

Re: Hi,

[Fernando Nasser]

Hi,

What version of cygwin are you using?  (from where did you get,
what is the snapshot date etc.)

Have you tried "make install" and to use the so installed version?


-- 
Fernando Nasser
Red Hat Canada Ltd.                     E-Mail:  fnasser@cygnus.com
2323 Yonge Street, Suite #300           Tel:  416-482-2661 ext. 311
Toronto, Ontario   M4P 2C9              Fax:  416-482-6299

Re: Hi,

[Jim Ingham]

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1492 bytes --]

Title: Re: Hi,



Ken,

Try running it from a DOS console window, you might get some error output spewed into the console that you can use.  The usual thing in this case is that Insight is not correctly finding the Tcl code that it needs to run.

Jim

Hi,
 
Cant get the GUI for insight to run.
 
I downloaded the Insight 5.0 release and was finally able to build it (new to this stuff).  When trying to run "gdb.exe" it briefly opens then closes a dos window, the GUI never runs.  If I run with the "--nw" option, then the command line version opens up normally.
 
I ran gdb within gdb and got the following output.
(gdb) run
Starting program: c:\gnu\insight-5.0\m68k-elf\gdb.exe
66600000:C:/GNU/INSIGHT-5.0/M68K-ELF/TIX4180.DLL
7fcb0000:C:/WINDOWS/SYSTEM/SHELL32.DLL
bfe90000:C:/WINDOWS/SYSTEM/COMCTL32.DLL
70bd0000:C:/WINDOWS/SYSTEM/SHLWAPI.DLL
7fe10000:C:/WINDOWS/SYSTEM/COMDLG32.DLL
66300000:C:/GNU/INSIGHT-5.0/M68K-ELF/CYGTK80.DLL
66800000:C:/GNU/INSIGHT-5.0/M68K-ELF/CYGITK30.DLL
bfe80000:C:/WINDOWS/SYSTEM/ADVAPI32.DLL
bff20000:C:/WINDOWS/SYSTEM/GDI32.DLL
bff50000:C:/WINDOWS/SYSTEM/USER32.DLL
bff70000:C:/WINDOWS/SYSTEM/KERNEL32.DLL
61000000:C:/GNU/INSIGHT-5.0/M68K-ELF/CYGWIN1.DLL
66000000:C:/GNU/INSIGHT-5.0/M68K-ELF/CYGTCL80.DLL
66700000:C:/GNU/INSIGHT-5.0/M68K-ELF/CYGITCL30.DLL
 
Program exited normally.
(gdb)
Any ideas on why the GUI is not running?
 
Running and compiling on Win98.   --host=i586-pc-cygwin  --target=m68k-elf
 
Thanks,
Kenneth Moore
 

Re: Hi,

[Chris Faylor]

On Wed, Jun 21, 2000 at 10:45:20AM -0700, Jim Ingham wrote:
>Try running it from a DOS console window, you might get some error output
>spewed into the console that you can use.  The usual thing in this case is
>that Insight is not correctly finding the Tcl code that it needs to run.

Actually, I think this is one of those inscrutable errors that go to
stderr in the brief time when there is no stderr as gdb is starting
up.

I've been discussing with Keith Seitz the best way to deal with these.
I have a really simple patch that just delays freeing the console until
the very last second.  This causes init.tcl errors to show up on the
console.

I don't really like this solution because if insight is started via a
mouse click you still get a flashing console with a stroboscopic
error message.

We were discussing trapping startup errors and displaying them in
a pop-up window but I don't think there is any simple mechanism for
doing that.

cgf

>Hi,
>
>Cant get the GUI for insight to run.
>
>I downloaded the Insight 5.0 release and was finally able to build it (new
>to this stuff).  When trying to run "gdb.exe" it briefly opens then closes a
>dos window, the GUI never runs.  If I run with the "--nw" option, then the
>command line version opens up normally.
>
>I ran gdb within gdb and got the following output.
>(gdb) run
>Starting program: c:\gnu\insight-5.0\m68k-elf\gdb.exe
>66600000:C:/GNU/INSIGHT-5.0/M68K-ELF/TIX4180.DLL
>7fcb0000:C:/WINDOWS/SYSTEM/SHELL32.DLL
>bfe90000:C:/WINDOWS/SYSTEM/COMCTL32.DLL
>70bd0000:C:/WINDOWS/SYSTEM/SHLWAPI.DLL
>7fe10000:C:/WINDOWS/SYSTEM/COMDLG32.DLL
>66300000:C:/GNU/INSIGHT-5.0/M68K-ELF/CYGTK80.DLL
>66800000:C:/GNU/INSIGHT-5.0/M68K-ELF/CYGITK30.DLL
>bfe80000:C:/WINDOWS/SYSTEM/ADVAPI32.DLL
>bff20000:C:/WINDOWS/SYSTEM/GDI32.DLL
>bff50000:C:/WINDOWS/SYSTEM/USER32.DLL
>bff70000:C:/WINDOWS/SYSTEM/KERNEL32.DLL
>61000000:C:/GNU/INSIGHT-5.0/M68K-ELF/CYGWIN1.DLL
>66000000:C:/GNU/INSIGHT-5.0/M68K-ELF/CYGTCL80.DLL
>66700000:C:/GNU/INSIGHT-5.0/M68K-ELF/CYGITCL30.DLL
>
>Program exited normally.
>(gdb)
>Any ideas on why the GUI is not running?
>
>Running and compiling on Win98.   --host=i586-pc-cygwin  --target=m68k-elf
>
>Thanks,
>Kenneth Moore
>
>
>
>

-- 
cgf@cygnus.com                        Cygnus Solutions, a Red Hat company
http://sourceware.cygnus.com/         http://www.redhat.com/

Re: Hi,

[Jim Ingham]

Chris,

> On Wed, Jun 21, 2000 at 10:45:20AM -0700, Jim Ingham wrote:
>> Try running it from a DOS console window, you might get some error output
>> spewed into the console that you can use.  The usual thing in this case is
>> that Insight is not correctly finding the Tcl code that it needs to run.
> 
> Actually, I think this is one of those inscrutable errors that go to
> stderr in the brief time when there is no stderr as gdb is starting
> up.
> 
> I've been discussing with Keith Seitz the best way to deal with these.
> I have a really simple patch that just delays freeing the console until
> the very last second.  This causes init.tcl errors to show up on the
> console.
> 
> I don't really like this solution because if insight is started via a
> mouse click you still get a flashing console with a stroboscopic
> error message.

Yeah, I don't like this at all.  I always thought that the flashing console
thingie was truely lame,. and made Insight look really bad. IIRC, the only
reason that we didn't build with -subsystem-windows (sic), and thus
eliminate this particular wart was that in the bad ole days the only way to
run the gdb testsuite on Windows was to telnet in and use expect, and that
required -subsystem-console.  Now that you can run the testsuite on Windows
successfully, there is no good reason for this.

> 
> We were discussing trapping startup errors and displaying them in
> a pop-up window but I don't think there is any simple mechanism for
> doing that.
> 

Yeah, I was hoping that you could do something really simple like register a
readable file-event for stderr, and respond to output there, but it looks
like Tcl doesn't open stderr readable, and I have no idea what havoc doing
this would wreak...  OTOH, things like the TkCon extension are able to
redirect all the standard channels into a text widget, all from Tcl.  It
might be a good idea to have a look at what TkCon does, and just copy that
early on in the startup process...

Jim

> cgf
> 
>> Hi,
>> 
>> Cant get the GUI for insight to run.
>> 
>> I downloaded the Insight 5.0 release and was finally able to build it (new
>> to this stuff).  When trying to run "gdb.exe" it briefly opens then closes a
>> dos window, the GUI never runs.  If I run with the "--nw" option, then the
>> command line version opens up normally.
>> 
>> I ran gdb within gdb and got the following output.
>> (gdb) run
>> Starting program: c:\gnu\insight-5.0\m68k-elf\gdb.exe
>> 66600000:C:/GNU/INSIGHT-5.0/M68K-ELF/TIX4180.DLL
>> 7fcb0000:C:/WINDOWS/SYSTEM/SHELL32.DLL
>> bfe90000:C:/WINDOWS/SYSTEM/COMCTL32.DLL
>> 70bd0000:C:/WINDOWS/SYSTEM/SHLWAPI.DLL
>> 7fe10000:C:/WINDOWS/SYSTEM/COMDLG32.DLL
>> 66300000:C:/GNU/INSIGHT-5.0/M68K-ELF/CYGTK80.DLL
>> 66800000:C:/GNU/INSIGHT-5.0/M68K-ELF/CYGITK30.DLL
>> bfe80000:C:/WINDOWS/SYSTEM/ADVAPI32.DLL
>> bff20000:C:/WINDOWS/SYSTEM/GDI32.DLL
>> bff50000:C:/WINDOWS/SYSTEM/USER32.DLL
>> bff70000:C:/WINDOWS/SYSTEM/KERNEL32.DLL
>> 61000000:C:/GNU/INSIGHT-5.0/M68K-ELF/CYGWIN1.DLL
>> 66000000:C:/GNU/INSIGHT-5.0/M68K-ELF/CYGTCL80.DLL
>> 66700000:C:/GNU/INSIGHT-5.0/M68K-ELF/CYGITCL30.DLL
>> 
>> Program exited normally.
>> (gdb)
>> Any ideas on why the GUI is not running?
>> 
>> Running and compiling on Win98.   --host=i586-pc-cygwin  --target=m68k-elf
>> 
>> Thanks,
>> Kenneth Moore
>> 
>> 
>> 
>> 

Re: Hi,

[Chris Faylor]

On Wed, Jun 21, 2000 at 01:26:41PM -0700, Jim Ingham wrote:
>Yeah, I don't like this at all.  I always thought that the flashing console
>thingie was truely lame,. and made Insight look really bad. IIRC, the only
>reason that we didn't build with -subsystem-windows (sic), and thus
>eliminate this particular wart was that in the bad ole days the only way to
>run the gdb testsuite on Windows was to telnet in and use expect, and that
>required -subsystem-console.  Now that you can run the testsuite on Windows
>successfully, there is no good reason for this.

I believe that if you use -subsystem=windows then 'gdb -nw' wouldn't
work.  Wasn't that the case?  I guess I should just check this.

I hate that flashing console window, too.  I spent some time trying to
get get rid of it a copule of years ago but it seemed like Microsoft had
gone out of their way to make it difficult to do anything at all
sophisticated with console windows.  The flashing console window was the
best available compromise.

>> We were discussing trapping startup errors and displaying them in
>> a pop-up window but I don't think there is any simple mechanism for
>> doing that.
>
>Yeah, I was hoping that you could do something really simple like register a
>readable file-event for stderr, and respond to output there, but it looks
>like Tcl doesn't open stderr readable, and I have no idea what havoc doing
>this would wreak...  OTOH, things like the TkCon extension are able to
>redirect all the standard channels into a text widget, all from Tcl.  It
>might be a good idea to have a look at what TkCon does, and just copy that
>early on in the startup process...

I think that Keith suggested something similar.  I've Cc'ed him.

cgf