From b136cd053f84c646cbdefeeb9a8ddbc55fd4acc6 Mon Sep 17 00:00:00 2001 From: Pedro Alves Date: Mon, 23 May 2011 15:18:36 +0000 Subject: [PATCH] 2011-05-23 Pedro Alves * infrun.c (user_visible_resume_ptid): Fix typos in describing comment. --- gdb/ChangeLog | 5 +++++ gdb/infrun.c | 6 +++--- 2 files changed, 8 insertions(+), 3 deletions(-) diff --git a/gdb/ChangeLog b/gdb/ChangeLog index ea55f7c935c..db94468ed53 100644 --- a/gdb/ChangeLog +++ b/gdb/ChangeLog @@ -1,3 +1,8 @@ +2011-05-23 Pedro Alves + + * infrun.c (user_visible_resume_ptid): Fix typos in describing + comment. + 2011-05-21 Mark Kettenis * sparc-nat.c (sparc_fetch_inferior_registers): Explicitly supply diff --git a/gdb/infrun.c b/gdb/infrun.c index 36d265cb175..1d8932ab21a 100644 --- a/gdb/infrun.c +++ b/gdb/infrun.c @@ -1604,9 +1604,9 @@ maybe_software_singlestep (struct gdbarch *gdbarch, CORE_ADDR pc) /* Return a ptid representing the set of threads that we will proceed, in the perspective of the user/frontend. We may actually resume fewer threads at first, e.g., if a thread is stopped at a - breakpoint that needs stepping-off, but that should be visible to - the user/frontend, and neither should the frontend/user be allowed - to proceed any of the threads that happen to be stopped at for + breakpoint that needs stepping-off, but that should not be visible + to the user/frontend, and neither should the frontend/user be + allowed to proceed any of the threads that happen to be stopped for internal run control handling, if a previous command wanted them resumed. */ -- 2.30.2