This is the mail archive of the gdb-patches@sources.redhat.com mailing list for the GDB project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: [RFA/MI testsuite] Add mi_runto


Keith Seitz writes:
 > On Tue, 10 Sep 2002, Elena Zannoni wrote:
 > 
 > > Yes, please. Thanks. It will be easier to maintain if we have only one
 > > copy of these functions.
 > 
 > UGH. Now I remember why I did this... mi_run_to_helper expects an MI 
 > command to execute, either "exec-continue" or "exec-run". There is no way 
 > for us to know this if we are attempting to run the inferior for the first 
 > time (or re-run it). This is usually handled by mi_run_cmd, and that is 
 > the difference between these to functions. They are essentially the same, 
 > otherwise. The best I can do is put the mi_gdb_test for the stop in 
 > anohter proc, but I think that would just mess the code up even more.
 > (mi_step and mi_next are okay, though).
 > 
 > Of course, it's your call.
 > Keith
 > 


Oh ok. mi_run_to executes an inferior that has already started.
While mi_runto starts it from scratch.

Could we rename mi_run_to to something like mi_execute_to instead?
It is used only in mi-var-cmd.exp.

And add your paragraph above in mi-support.exp as a comment?

Elena


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