public inbox for insight@sourceware.org
 help / color / mirror / Atom feed
From: Chris Faylor <cgf@cygnus.com>
To: Jim Ingham <jingham@apple.com>
Cc: Ken Moore <KMoore@gse-inc.com>, insight@sourceware.cygnus.com
Subject: Re: Hi,
Date: Wed, 21 Jun 2000 12:52:00 -0000	[thread overview]
Message-ID: <20000621155243.D24677@cygnus.com> (raw)
In-Reply-To: <B5764D40.1868%jingham@apple.com>

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/

  reply	other threads:[~2000-06-21 12:52 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-06-21  6:58 Hi, Ken Moore
2000-06-21  7:06 ` Hi, Fernando Nasser
2000-06-21 11:29 ` Hi, Jim Ingham
2000-06-21 12:52   ` Chris Faylor [this message]
2000-06-21 13:26     ` Hi, Jim Ingham
2000-06-21 13:48       ` Hi, Chris Faylor
2000-06-21  8:07 Hi, Ken Moore
2000-06-21  8:33 ` Hi, Fernando Nasser
2000-06-21  8:40 ` Hi, Chris Faylor
2000-06-21 13:43 Hi, Ken Moore

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20000621155243.D24677@cygnus.com \
    --to=cgf@cygnus.com \
    --cc=KMoore@gse-inc.com \
    --cc=insight@sourceware.cygnus.com \
    --cc=jingham@apple.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).