This is the mail archive of the insight@sources.redhat.com mailing list for the Insight project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]

[RFC] Why won't we debug exe's with no debug info?


Hi,

I was playing around with insight the other day and I noticed that when I
try to debug a program with no debug info, we get a warning message that
the program has no debug info, and then it refuses to let me debug it!!

I think this must be some silly remnant of Insight's haunted past, so I am
gonna whack this unless someone can give me reasons to keep it.

Keith

ChangeLog
2001-10-02  Keith Seitz <keiths@redhat.com>

	* library/interface.tcl (set_exe): If we're asked to debug
	an executable with no debug info, do it!

Patch
Index: library/interface.tcl
===================================================================
RCS file: /cvs/src/src/gdb/gdbtk/library/interface.tcl,v
retrieving revision 1.29
diff -u -p -r1.29 interface.tcl
--- interface.tcl	2001/08/13 18:30:36	1.29
+++ interface.tcl	2001/10/02 20:13:55
@@ -845,13 +845,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



Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]