gdb and binutils branch master updated. 763905a3ad8f98d33bd9319790a8d53904554265

[qiyao at sourceware dot org]

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  763905a3ad8f98d33bd9319790a8d53904554265 (commit)
      from  71e396f920e593494b8d57114d32e2c07f823781 (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=763905a3ad8f98d33bd9319790a8d53904554265

commit 763905a3ad8f98d33bd9319790a8d53904554265
Author: Yao Qi <yao@codesourcery.com>
Date:   Mon Oct 27 16:37:38 2014 +0800

    Fix trace file fails on powerpc64
    
    I see the following fails on powerpc64-linux,
    
    (gdb) target tfile tfile-basic.tf^M
    warning: Uploaded tracepoint 1 has no source location, using raw address^M
    Tracepoint 1 at 0x10012358^M
    Created tracepoint 1 for target's tracepoint 1 at 0x10012358.^M
    (gdb) PASS: gdb.trace/tfile.exp: target tfile tfile-basic.tf
    info trace^M
    Num     Type           Disp Enb Address            What^M
    1       tracepoint     keep y   0x0000000010012358 <write_basic_trace_file>^M
            installed on target^M
    (gdb) FAIL: gdb.trace/tfile.exp: info tracepoints on trace file
    
    -target-select tfile tfile-basic.tf^M
    =thread-group-started,id="i1",pid="1"^M
    =thread-created,id="1",group-id="i1"^M
    &"warning: Uploaded tracepoint 1 has no source location, using raw address\n"^M
    =breakpoint-created,bkpt={number="1",type="tracepoint",disp="keep",enabled="y",
    addr="0x0000000010012358",at="<write_basic_trace_file>",thread-groups=["i1"],
    times="0",installed="y",original-location="*0x10012358"}^M
    ~"Created tracepoint 1 for target's tracepoint 1 at 0x10012358.\n"^M
    ^connected^M
    (gdb) ^M
    FAIL: gdb.trace/mi-traceframe-changed.exp: tfile: select trace file
    
    These fails are caused by writing function descriptor address into trace
    file instead of function address.  This patch is to teach tfile.c to
    write function address on powerpc64 target.  With this patch applied,
    fails in tfile.exp and mi-traceframe-changed.exp are fixed.  Is it
    OK?
    
    gdb/testsuite:
    
    2014-10-27  Yao Qi  <yao@codesourcery.com>
    
    	* gdb.trace/tfile.c (adjust_function_address)
    	[__powerpc64__ && _CALL_ELF != 2]: Get function address from
    	function descriptor.

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

Summary of changes:
 gdb/testsuite/ChangeLog         |    6 ++++++
 gdb/testsuite/gdb.trace/tfile.c |    3 +++
 2 files changed, 9 insertions(+), 0 deletions(-)


hooks/post-receive
-- 
gdb and binutils