From mboxrd@z Thu Jan  1 00:00:00 1970
From: tromey@redhat.com
To: insight-gnats@sourceware.cygnus.com
Subject: insight/88: shouldn't have to set target to Exec on native builds
Date: Mon, 14 May 2001 09:43:00 -0000
Message-id: <20010514163351.3798.qmail@sourceware.cygnus.com>
X-SW-Source: 2001-q2/msg00002.html
List-Id: <insight-prs.sourceware.org>

>Number:         88
>Category:       insight
>Synopsis:       shouldn't have to set target to Exec on native builds
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Mon May 14 09:43:01 PDT 2001
>Closed-Date:
>Last-Modified:
>Originator:     Tom Tromey
>Release:        unknown-1.0
>Organization:
>Environment:

>Description:
[ this is cut-and-pasted from my email to the insight list ]

I'm using a relatively recent (yesterday) cvs Insight.
I run x86 Red Hat Linux 6.2.

The `Run' button on the toolbar doesn't seem to work for me.
I start gdb on my program.
The arguments to the program and a breakpoint are already set by
.gdbinit in the current directory.

When I hit Run, apparently nothing happens.
This message appears in the insight console window:

    Argument required (target name).  Try `help target'


Of course, what I forgot is that I have to go to the target settings
dialog and set the target to Exec.  Unfortunately this also has the
side effect of overwriting the inferior arguments (I consider this is
a minor problem since I know at least they'll be saved for next time).

I dislike having to remember to do this.  In fact I forget regularly,
and then I forget the fix, and end up just using `r' in the console.

I think this is a fairly important bug to fix for native
configurations at least.  Probably more than 90% of debugging with a
native linux gdb is done with the Exec target.  Having to always set
this means insight isn't optimized for the common case.
>How-To-Repeat:

>Fix:

>Release-Note:
>Audit-Trail:
>Unformatted: