From 3cecbbbef197fdcdc833155ba4c3f3233a10e5c7 Mon Sep 17 00:00:00 2001 From: Tom Tromey Date: Mon, 28 Jul 2014 12:53:35 -0600 Subject: 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 * target.c (set_targetdebug): New function. (initialize_targets): Pass set_targetdebug when creating "set debug target". 2014-08-04 Tom Tromey * gdb.texinfo (Debugging Output): Update for change to "set debug target". 2014-08-04 Tom Tromey * gdb.base/sss-bp-on-user-bp-2.exp: Expect output from "set debug target 0". --- gdb/doc/ChangeLog | 5 +++++ gdb/doc/gdb.texinfo | 3 +-- 2 files changed, 6 insertions(+), 2 deletions(-) (limited to 'gdb/doc') diff --git a/gdb/doc/ChangeLog b/gdb/doc/ChangeLog index 20ce293..2bf94bc 100644 --- a/gdb/doc/ChangeLog +++ b/gdb/doc/ChangeLog @@ -1,3 +1,8 @@ +2014-08-04 Tom Tromey + + * gdb.texinfo (Debugging Output): Update for change to "set debug + target". + 2014-08-01 Masaki Muranaka Pushed by Joel Brobecker . diff --git a/gdb/doc/gdb.texinfo b/gdb/doc/gdb.texinfo index 32f709a..8d9148c 100644 --- a/gdb/doc/gdb.texinfo +++ b/gdb/doc/gdb.texinfo @@ -22996,8 +22996,7 @@ Show the current state of symbol table creation debugging. Turns on or off display of @value{GDBN} target debugging info. This info includes what is going on at the target level of GDB, as it happens. The default is 0. Set it to 1 to track events, and to 2 to also track the -value of large memory transfers. Changes to this flag do not take effect -until the next time you connect to a target or use the @code{run} command. +value of large memory transfers. @item show debug target Displays the current state of displaying @value{GDBN} target debugging info. -- cgit v1.1