From mboxrd@z Thu Jan  1 00:00:00 1970
From: Mo DeJong <mdejong@cygnus.com>
To: insight@sourceware.cygnus.com
Subject: Insight bug, run command can't be put in --command file.
Date: Wed, 12 Jul 2000 01:45:00 -0000
Message-id: <Pine.SOL.3.91.1000712013808.25069E-100000@cse.cygnus.com>
X-SW-Source: 2000-q3/msg00054.html

We have a set of commands that starts up Source-Navigator
in "regular" or "debug" mode. Like so:

echo "set args -- -home $prefix ${1+"$@"}" > gdb.run
#echo "run" >> gdb.run
exec gdb --command gdb.run $bindir/hyper

When using command line gdb, you can uncomment
the "run" line (so that it get added to the gdb.run file)
and gdb will start up just fine. If you try it with
insight, then the main GUI windows never show up.

This is kind of handy, as insight stays hidden
as your GUI application runs. Problem is, if the
application gets hit with a signal, Insight will
just display the "Signal Caught" dialog box
and then exit. It would be really nice if
Insight could show the little dialog and
then bring up the main insight windows
instead of doing an exit at that point.

If you do not put the "run" command in the file,
then insight starts up the normal way and
everything works as expected.

Mo DeJong
Red Hat Inc