Home
last modified time | relevance | path

Searched refs:mi_proceeded (Results 1 – 5 of 5) sorted by relevance

/netbsd/src/external/gpl3/gdb/dist/gdb/mi/
Dmi-interp.c463 this->mi_proceeded = 1; in on_about_to_proceed()
672 if (!mi->running_result_record_printed && mi->mi_proceeded) in mi_on_resume_1()
688 if (!mi->running_result_record_printed && mi->mi_proceeded) in mi_on_resume_1()
Dmi-interp.h104 int mi_proceeded; variable
Dmi-main.c1820 mi->mi_proceeded = 0; in captured_mi_execute_command()
/netbsd/src/external/gpl3/gdb/dist/gdb/
DChangeLog-200911046 * mi-main.h (mi_proceeded): Declare.
11047 * mi/mi-main.c (mi_cmd_execute): Clear mi_proceeded before running
/netbsd/src/external/gpl3/binutils/dist/
DChangeLog.git47024 I stumbled on the mi_proceeded and running_result_record_printed
47059 running_result_record_printed and mi_proceeded globals.
47060 mi_about_to_proceed then sets mi_proceeded. Then, mi_on_resume_1 gets
47063 !running_result_record_printed && mi_proceeded