RFC: Changes to the "Run" button behavior

RFC: Changes to the "Run" button behavior

[Fernando Nasser]

There are situations where GDB is being used to debug ROM code
(BIOS for instance) and there is no executable involved.
The programmer is just doing assembler level debugging, with no
symbols, just plain raw binary data -- like in the god olde times :-)

Regardless of what you say in the Target Selection dialog, the 
"Run" will ask for a file if you press the button.
The user has to either use the continue button or specify a dummy exec
file just to placate this piece of code.
It is sort of annoying having the RUN button in there but not being able
to use it, specially because it turns into the STOP button that you may
want to press and you end up having to race with the mouse.

I think it should require the executable file only if the target is "native".
If the target is remote, the "Load" code is the one that should require
the file to be present.

In this case, the user will not load anything, and will unset the "load"
option in the Target Selection dialog, so it will be able to use the RUN 
button.


Any objections?





-- 
Fernando Nasser
Red Hat Canada Ltd.                     E-Mail:  fnasser@redhat.com
2323 Yonge Street, Suite #300
Toronto, Ontario   M4P 2C9

Re: RFC: Changes to the "Run" button behavior

[Steven Johnson]

Fernando Nasser wrote:
> 
> 
> In this case, the user will not load anything, and will unset the "load"
> option in the Target Selection dialog, so it will be able to use the RUN
> button.
> 
> Any objections?
> 

Sounds good to me.

Steven.