This is the mail archive of the gdb-cvs@sourceware.org mailing list for the GDB project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

gdb and binutils branch master updated. 568e808b7d80a7613c1b6d94ff93dd517436b249


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  568e808b7d80a7613c1b6d94ff93dd517436b249 (commit)
      from  467d141bf5399b1092118981da1143523b19b896 (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=568e808b7d80a7613c1b6d94ff93dd517436b249

commit 568e808b7d80a7613c1b6d94ff93dd517436b249
Author: Markus Metzger <markus.t.metzger@intel.com>
Date:   Tue Dec 3 10:20:47 2013 +0100

    btrace: initiate teardown when closing record btrace target
    
    The to_teardown_btrace target method is used to free btrace resources
    during shutdown when target record has already been unpushed and we
    can't reliably talk to a remote target to disable branch tracing.
    
    Tracing resources are freed for each thread when the thread is removed;
    both on the GDB side and on the gdbserver side.
    
    In the remote case, the remote target that provides to_teardown_btrace
    to free the GDB side resources has already been unpushed when threads
    are destroyed.  This results in a complaint "You can't do this ..." and
    in a few bytes of memory leaked for each thread.
    
    Initiate btrace teardown in record_btrace_close, so the remote target is
    still in place.
    
    2014-01-27  Markus Metzger  <markus.t.metzger@intel.com>
    
    	* record-btrace.c (record_btrace_close): Call btrace_teardown
    	for all threads.

-----------------------------------------------------------------------

Summary of changes:
 gdb/ChangeLog       |    5 +++++
 gdb/record-btrace.c |    7 ++++++-
 2 files changed, 11 insertions(+), 1 deletions(-)


hooks/post-receive
-- 
gdb and binutils


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]