From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jim Ingham To: Chris Faylor Cc: Ken Moore , Subject: Re: Hi, Date: Wed, 21 Jun 2000 13:26:00 -0000 Message-id: References: <20000621155243.D24677@cygnus.com> X-SW-Source: 2000-q2/msg00300.html 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 >> >> >> >>