Don't call set_gdbarch_cannot_step_breakpoint in aarch64_gdbarch_init

[deliverable/binutils-gdb.git] / gdb / ChangeLog

diff --git a/gdb/ChangeLog b/gdb/ChangeLog
index cfbd576d5b83ae28e10b5d9cf5a66937ab32b487..ad074c36763a75bdb1993840f336ad5a84d113b1 100644 (file)
--- a/gdb/ChangeLog
+++ b/gdb/ChangeLog
@@ -1,7 +1,20 @@
-2015-03-19 Pedro Alves  <palves@redhat.com>
+2015-03-20  Yao Qi  <yao.qi@linaro.org>
 
-       * linux-low.c (count_events_callback, select_event_lwp_callback):
-       Use the lwp's status_pending_p field, not the thread's.
+       * aarch64-tdep.c (aarch64_gdbarch_init): Don't call
+       set_gdbarch_cannot_step_breakpoint.
+
+2015-03-19  Pedro Alves  <palves@redhat.com>
+
+       * linux-nat.c (linux_resume_one_lwp): Rename to ...
+       (linux_resume_one_lwp_throw): ... this.  Don't handle ESRCH here,
+       instead call perror_with_name.
+       (check_ptrace_stopped_lwp_gone): New function.
+       (linux_resume_one_lwp): Reimplement as wrapper around
+       linux_resume_one_lwp_throw that swallows errors if the LWP is
+       gone.
+       (resume_stopped_resumed_lwps): Try register reads in TRY/CATCH and
+       swallows errors if the LWP is gone.  Use
+       linux_resume_one_lwp_throw instead of linux_resume_one_lwp.
 
 2015-03-19  Pedro Alves  <palves@redhat.com>