gdb and binutils branch master updated. 9810b41048d4fc230ec5e124ecdead4a3a9598ec

[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  9810b41048d4fc230ec5e124ecdead4a3a9598ec (commit)
      from  048ea17465ce5effe702895cd644fa3d9dd94680 (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=9810b41048d4fc230ec5e124ecdead4a3a9598ec

commit 9810b41048d4fc230ec5e124ecdead4a3a9598ec
Author: Yao Qi <yao@codesourcery.com>
Date:   Sat Mar 29 09:41:02 2014 +0800

    Escape backslash in windows path
    
    Hi,
    On windows host, we see the following ERROR,
    
    (gdb) PASS: gdb.base/setshow.exp: set history filename ~/foobar.baz
    ERROR OCCURED: couldn't compile regular expression pattern: invalid escape \ seq
    uence
        while executing
    "expect -nobrace -i exp13 -timeout 10 -re {.*A problem internal to GDB has been
    detected} {
    	    fail "$message (GDB internal error)"
    	    gdb_internal..."
        invoked from within
    "expect {
    -i exp13 -timeout 10
    	-re ".*A problem internal to GDB has been detected" {
    	    fail "$message (GDB internal error)"
    	    gdb_internal_erro..."
        ("uplevel" body line 1)
        invoked from within
    "uplevel $body" REGEXP REG_EESCAPE {invalid escape \ sequence} couldn't compile
    regular expression pattern: invalid escape \ sequenceERROR: Process no longer ex
    ists
    
    which leads to
    UNRESOLVED: gdb.base/setshow.exp: show history filename (~/foobar.baz)
    
    and this error is thrown from this test below:
    
    gdb_test "show history filename" \
        "The filename in which to record the command history is \"$HOME/foobar.baz\"..*" \
        "show history filename (~/foobar.baz)"
    
    HOME is a windows path, like C:\foo\bar.  When it is used in gdb_test to match
    output, the error is thrown because backslash is a special character in
    regular expression.  This patch is to escape backslash to fix this
    error by using string_to_regexp.
    
    gdb/testsuite:
    
    2014-04-03  Yao Qi  <yao@codesourcery.com>
    
    	* gdb.base/setshow.exp: Invoke string_to_regexp to HOME and PWD.

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

Summary of changes:
 gdb/testsuite/ChangeLog            |    4 ++++
 gdb/testsuite/gdb.base/setshow.exp |    4 ++--
 2 files changed, 6 insertions(+), 2 deletions(-)


hooks/post-receive
-- 
gdb and binutils