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. 33aeebcf589077c82b63815645ca95f20dc064d0


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  33aeebcf589077c82b63815645ca95f20dc064d0 (commit)
      from  7b4159018eeef7e1c682c63c1b33ce9c064e7c65 (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=33aeebcf589077c82b63815645ca95f20dc064d0

commit 33aeebcf589077c82b63815645ca95f20dc064d0
Author: Maciej W. Rozycki <macro@codesourcery.com>
Date:   Tue Sep 9 17:39:17 2014 +0100

    GDB/testsuite: Correct gdb.base/watchpoint-solib.exp timeout tweak
    
    Similarly to the previous changes to gdb.reverse/sigall-reverse.exp and
    gdb.reverse/until-precsave.exp this corrects the timeout tweak in
    gdb.base/watchpoint-solib.exp.
    
    This test case executes a large amount of code with a software watchpoint
    enabled.  This means single-stepping all the way through and takes a lot
    of time, e.g. for an ARMv7 Panda board and a `-march=armv5te' multilib:
    
    PASS: gdb.base/watchpoint-solib.exp: continue to foo again
    elapsed: 714
    
    for the same board and a `-mthumb -march=armv5te' multilib:
    
    PASS: gdb.base/watchpoint-solib.exp: continue to foo again
    elapsed: 1275
    
    and for QEMU in the system emulation mode and a `-march=armv4t'
    multilib:
    
    PASS: gdb.base/watchpoint-solib.exp: continue to foo again
    elapsed: 115
    
    (values in seconds) -- all of which having the default timeout of 60s,
    set based on the requirement of the remaining test cases (other than
    gdb.reverse ones).
    
    Here again the timeout extension to have a meaning should be calculated
    by scaling rather than using an arbitrary constant, and a larger factor
    of 30 will do, leaving some margin.  Hopefully for everyone or otherwise
    we'll probably have to come up with a smarter solution.
    
    OTOH the other test cases in this script do not require the extension so
    they can be moved outside its umbrella so as to avoid unnecessary delays
    if something goes wrong and a genuine timeout triggers.
    
    	* gdb.base/watchpoint-solib.exp: Increase the timeout by a factor
    	of 30 rather than hardcoding 120 for a slow test case.  Take the
    	`gdb,timeout' target setting into account for this calculation.
    	Don't extend the timeout for the test cases that don't need it.

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

Summary of changes:
 gdb/testsuite/ChangeLog                     |    7 +++++++
 gdb/testsuite/gdb.base/watchpoint-solib.exp |   18 +++++++++++++-----
 2 files changed, 20 insertions(+), 5 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]