Use do_target_resume when stepping past permanent breakpoint too

We can use the recently added do_target_resume do simplify the code a
bit here.

Tested on x86_64 Fedora 20.

gdb/ChangeLog:
2015-04-01  Pedro Alves  <palves@redhat.com>

	* infrun.c (resume) <step past permanent breakpoint>: Use
	do_target_resume.
This commit is contained in:
Pedro Alves 2015-04-01 14:24:54 +00:00
parent 2ee52aa428
commit 1ac806b8a7
2 changed files with 7 additions and 7 deletions

View File

@ -1,3 +1,8 @@
2015-04-01 Pedro Alves <palves@redhat.com>
* infrun.c (resume) <step past permanent breakpoint>: Use
do_target_resume.
2015-04-01 Pedro Alves <palves@redhat.com> 2015-04-01 Pedro Alves <palves@redhat.com>
* linux-nat.c (linux_handle_extended_wait): Always call set_running. * linux-nat.c (linux_handle_extended_wait): Always call set_running.

View File

@ -2184,17 +2184,12 @@ resume (enum gdb_signal sig)
thread advanced also" branch to be taken. IOW, we thread advanced also" branch to be taken. IOW, we
don't want this thread to step further from PC don't want this thread to step further from PC
(overstep). */ (overstep). */
gdb_assert (!step_over_info_valid_p ());
insert_single_step_breakpoint (gdbarch, aspace, pc); insert_single_step_breakpoint (gdbarch, aspace, pc);
insert_breakpoints (); insert_breakpoints ();
tp->suspend.stop_signal = GDB_SIGNAL_0;
/* We're continuing with all breakpoints inserted. It's
safe to let the target bypass signals. */
target_pass_signals ((int) GDB_SIGNAL_LAST, signal_pass);
/* ... and safe to let other threads run, according to
schedlock. */
resume_ptid = user_visible_resume_ptid (user_step); resume_ptid = user_visible_resume_ptid (user_step);
target_resume (resume_ptid, 0, GDB_SIGNAL_0); do_target_resume (resume_ptid, 0, GDB_SIGNAL_0);
discard_cleanups (old_cleanups); discard_cleanups (old_cleanups);
return; return;
} }