[ob] Correct ovldbreak.exp KFAILs

[Daniel Jacobowitz <drow@false.org>]

Tom confirmed for me that GDB is expected to print \3 instead of \003
nowadays.  This change caused a PASS -> KFAIL transition that I
noticed when diffing logs.  Fix tested on x86_64-linux and committed.

-- 
Daniel Jacobowitz
CodeSourcery

2009-07-06  Daniel Jacobowitz  <dan@codesourcery.com>

	* gdb.cp/ovldbreak.exp: Update expected output for character constants.

Index: gdb.cp/ovldbreak.exp
===================================================================
RCS file: /cvs/src/src/gdb/testsuite/gdb.cp/ovldbreak.exp,v
retrieving revision 1.11
diff -u -p -r1.11 ovldbreak.exp
--- gdb.cp/ovldbreak.exp	3 Jan 2009 05:58:04 -0000	1.11
+++ gdb.cp/ovldbreak.exp	6 Jul 2009 19:18:14 -0000
@@ -341,9 +341,9 @@ proc continue_to_bp_overloaded {might_kf
 }
 
 continue_to_bp_overloaded 0 25 "(void|)" ""
-continue_to_bp_overloaded 1 24 "char" "arg=2 \\'\\\\002\\'"
-continue_to_bp_overloaded 1 23 "signed char" "arg=3 \\'\\\\003\\'"
-continue_to_bp_overloaded 1 22 "unsigned char" "arg=4 \\'\\\\004\\'"
+continue_to_bp_overloaded 1 24 "char" "arg=2 \\'\\\\2\\'"
+continue_to_bp_overloaded 1 23 "signed char" "arg=3 \\'\\\\3\\'"
+continue_to_bp_overloaded 1 22 "unsigned char" "arg=4 \\'\\\\4\\'"
 continue_to_bp_overloaded 1 21 "short" "arg=5"
 continue_to_bp_overloaded 1 20 "unsigned short" "arg=6"
 continue_to_bp_overloaded 0 19 "int" "arg=7"