This is the mail archive of the
gdb-cvs@sourceware.org
mailing list for the GDB project.
gdb and binutils branch master updated. 2b59118e727300b1c4e306e08ac53ee5693ab45b
- From: willnewton at sourceware dot org
- To: gdb-cvs at sourceware dot org
- Date: 20 Nov 2013 10:50:49 -0000
- Subject: gdb and binutils branch master updated. 2b59118e727300b1c4e306e08ac53ee5693ab45b
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "gdb and binutils".
The branch, master has been updated
via 2b59118e727300b1c4e306e08ac53ee5693ab45b (commit)
from b26dfc9ab352692e0bb8b005b9ca58eb1bc8c026 (commit)
Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.
- Log -----------------------------------------------------------------
https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=2b59118e727300b1c4e306e08ac53ee5693ab45b
commit 2b59118e727300b1c4e306e08ac53ee5693ab45b
Author: Will Newton <will.newton@linaro.org>
Date: Fri Nov 8 16:26:10 2013 +0000
gdb/arm-tdep.c: Remove "Infinite loop detected" error message.
Since as far back as the beginning of the sourceware repository
the ARM port has printed an error "Infinite loop detected" when
the next_pc calculated is the same as the current one, for example
when encountering a branch to the current PC address.
This causes the test gdb.base/random-signal.exp as the error message
is not expected. I have not been able to find a good reason for the
message to be here so remove it and let the test pass.
gdb/ChangeLog:
2013-11-20 Will Newton <will.newton@linaro.org>
* arm-tdep.c (arm_get_next_pc): Remove "Infinite loop detected"
error message.
-----------------------------------------------------------------------
Summary of changes:
gdb/ChangeLog | 5 +++++
gdb/arm-tdep.c | 12 ++----------
2 files changed, 7 insertions(+), 10 deletions(-)
hooks/post-receive
--
gdb and binutils