Escape backslash in windows path
Commit Message
On 03/29/2014 02:04 PM, Keith Seitz wrote:
>> + # Escape backslash in case HOME is a windows path.
>> > + regsub -all {\\} $HOME {\\\\} HOME
>> > pass $test
>> > }
>> > }
> Does string_to_regexp work for this?
Yes, I didn't know this procedure before. Update the patch using
string_to_regexp.
Comments
On 03/31/2014 09:04 AM, Yao Qi wrote:
> gdb/testsuite:
>
> 2014-03-31 Yao Qi <yao@codesourcery.com>
>
> * gdb.base/setshow.exp: Invoke string_to_regexp to HOME and PWD.
Patch is pushed in.
@@ -179,7 +179,7 @@ gdb_test_no_output "set history filename ~/foobar.baz" \
"set history filename ~/foobar.baz"
#test show history filename ~/foobar.baz
gdb_test "show history filename" \
- "The filename in which to record the command history is \"$HOME/foobar.baz\"..*" \
+ "The filename in which to record the command history is \"[string_to_regexp $HOME]/foobar.baz\"..*" \
"show history filename (~/foobar.baz)"
#get current working directory
set PWD ""
@@ -195,7 +195,7 @@ gdb_test_no_output "set history filename foobar.baz" \
"set history filename foobar.baz"
#test show history filename foobar.baz
gdb_test "show history filename" \
- "The filename in which to record the command history is \"$PWD/foobar.baz\"..*" \
+ "The filename in which to record the command history is \"[string_to_regexp $PWD]/foobar.baz\"..*" \
"show history filename (current_directory/foobar.baz)"
#test set history save on
gdb_test_no_output "set history save on" "set history save on"