I've checked in the attached patch that fixes some long-standing Run button 
problems.

- Previously, Insight remembered the target name last used when debugging an 
executable.  It would then attempt to attach to that target the next time it 
was run with the same executable.  Unfortunately it did not remember the
target options (port number, etc) or set the baud rate.  Those were saved as
global preferences, so often Insight failed to connect. This patch should fix 
all these issues.

- With this patch the Run button is made busy (changes to stop sign) when 
target command is issued.  This makes it possible to cancel.

- When debugging a program, if you hit the Run button, it restarts 
immediately.  This patch instead puts up a dialog allowing you to confirm or 
cancel restarting.  This is consistent with the command line behavior.

-- 
Martin Hunt
GDB Engineer
Red Hat, Inc.

2002-10-10  Martin M. Hunt  <hunt@redhat.com>

	* library/session.tcl (save): Save target_cmd,
	attach, load, run, and cont as session prefs.
	(notice_file_change): Load in above session
	prefs.
	
	* library/interface.tcl (set_target): Set icons busy
	before attempting target command and set back to idle after.
	(run_executable): Return on ATTACH_ERROR.
	(gdbtk_run): If run button is hit when a program
	is currently being debugged, put up a dialog allowing
	user to continue or cancel.