Searched refs:running_result_record_printed (Results 1 – 5 of 5) sorted by relevance
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()690 mi->running_result_record_printed = 1; in mi_on_resume_1()
100 int running_result_record_printed = 1; variable
1819 mi->running_result_record_printed = 0; in captured_mi_execute_command()1839 if (!mi->running_result_record_printed) in captured_mi_execute_command()1878 if (!mi->running_result_record_printed) in captured_mi_execute_command()
6667 * mi/mi-main.c (running_result_record_printed): New.6669 running_result_record_printed. Use running_result_record_printed6672 * mi/mi-main.h (current_token, running_result_record_printed):
47024 I stumbled on the mi_proceeded and running_result_record_printed47059 running_result_record_printed and mi_proceeded globals.47063 !running_result_record_printed && mi_proceeded47066 running_result_record_printed. When mi_on_resume_1 gets called for the47067 second interpreter, running_result_record_printed is already set, so47083 running_result_record_printed flag get cleared, and therefore only or