This is the mail archive of the
gdb-cvs@sourceware.org
mailing list for the GDB project.
gdb and binutils branch master updated. 3cecbbbef197fdcdc833155ba4c3f3233a10e5c7
- From: tromey at sourceware dot org
- To: gdb-cvs at sourceware dot org
- Date: 4 Aug 2014 14:13:23 -0000
- Subject: gdb and binutils branch master updated. 3cecbbbef197fdcdc833155ba4c3f3233a10e5c7
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 3cecbbbef197fdcdc833155ba4c3f3233a10e5c7 (commit)
via 00b51ff5835770104952dca3f9addb8f1025a24b (commit)
from 78a4993b90b00289d015305a9eb1948fab9baf91 (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=3cecbbbef197fdcdc833155ba4c3f3233a10e5c7
commit 3cecbbbef197fdcdc833155ba4c3f3233a10e5c7
Author: Tom Tromey <tromey@redhat.com>
Date: Mon Jul 28 12:53:35 2014 -0600
make "set debug target" take effect immediately
Right now, "set debug target" acts a bit strangely.
Most target APIs only notice that it has changed when the target stack
is changed in some way. This is because many methods implement the
setting using the special debug target. However, a few spots do
change their behavior immediately -- any place explicitly checking
"targetdebug".
Some of this peculiar behavior is documented. However, I think that
it just isn't very useful for it to work this way. So, this patch
changes "set debug target" to take effect immediately in all cases.
This is done by simply calling update_current_target when the setting
is changed.
This required one small change in the test suite. Here a test was
expecting the current behavior.
Built and regtested on x86-64 Fedora 20.
2014-08-04 Tom Tromey <tromey@redhat.com>
* target.c (set_targetdebug): New function.
(initialize_targets): Pass set_targetdebug when creating "set
debug target".
2014-08-04 Tom Tromey <tromey@redhat.com>
* gdb.texinfo (Debugging Output): Update for change to "set debug
target".
2014-08-04 Tom Tromey <tromey@redhat.com>
* gdb.base/sss-bp-on-user-bp-2.exp: Expect output from "set debug
target 0".
https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=00b51ff5835770104952dca3f9addb8f1025a24b
commit 00b51ff5835770104952dca3f9addb8f1025a24b
Author: Tom Tromey <tromey@redhat.com>
Date: Tue Jul 29 13:31:00 2014 -0600
fix test suite regression
This fixes a test suite regession that Yao noticed.
This test checks for some specific "target debug" output
that has changed since the test was written.
2014-08-04 Tom Tromey <tromey@redhat.com>
* gdb.base/sss-bp-on-user-bp-2.exp: Match "to_resume", not
"target_resume".
-----------------------------------------------------------------------
Summary of changes:
gdb/ChangeLog | 6 ++++++
gdb/doc/ChangeLog | 5 +++++
gdb/doc/gdb.texinfo | 3 +--
gdb/target.c | 14 +++++++++++---
gdb/testsuite/ChangeLog | 10 ++++++++++
gdb/testsuite/gdb.base/sss-bp-on-user-bp-2.exp | 6 +++---
6 files changed, 36 insertions(+), 8 deletions(-)
hooks/post-receive
--
gdb and binutils