From mboxrd@z Thu Jan  1 00:00:00 1970
From: Keith Seitz <keiths@cygnus.com>
To: Insight Maling List <insight@sources.redhat.com>
Subject: What to do when no debug info?
Date: Wed, 17 Oct 2001 12:14:00 -0000
Message-id: <Pine.GSO.4.33.0110171212490.11927-100000@makita.cygnus.com>
X-SW-Source: 2001-q4/msg00145.html

Hi,

For a long, long time now, Insight has, for historical reasons, disallowed
the debugging of executables with no debug information when opened with
the File->Open... menu.

Anyone see any reason whatsoever that this restriction shouldn't be nuked?
Keith

PS. Proposed patch:
Index: gdbtk/library/interface.tcl
===================================================================
RCS file: /cvs/src/src/gdb/gdbtk/library/interface.tcl,v
retrieving revision 1.30
diff -u -p -r1.30 interface.tcl
--- interface.tcl	2001/10/06 18:10:50	1.30
+++ interface.tcl	2001/10/17 19:12:27
@@ -860,13 +860,6 @@ proc set_exe {} {
       set gdb_exe_name {}
       set file_done 0
       return
-    } elseif {[string match {*no debugging symbols found*} $msg]} {
-      tk_messageBox -icon error -default ok \
-	-title "GDB" -type ok -modal system \
-	-message "This executable has no debugging information."
-      set gdb_exe_name {}
-      set file_done 0
-      return
     }

     # force new target command