This is the mail archive of the
insight@sources.redhat.com
mailing list for the Insight project.
Re: What to do when no debug info?
- To: Keith Seitz <keiths at cygnus dot com>, Insight Maling List <insight at sources dot redhat dot com>
- Subject: Re: What to do when no debug info?
- From: "Martin M. Hunt" <hunt at redhat dot com>
- Date: Wed, 17 Oct 2001 13:05:02 -0700
- Organization: Red Hat Inc
- References: <Pine.GSO.4.33.0110171212490.11927-100000@makita.cygnus.com>
Perhaps a warning would be more appropriate. It seems to me this dialog was
inserted because someone was upset that GDB wasn't detecting that he was
trying to run a source debugger on an executable that couldn't be debugged.
On Wednesday 17 October 2001 12:14 pm, Keith Seitz wrote:
> 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