aboutsummaryrefslogtreecommitdiff
path: root/symlink-tree
diff options
context:
space:
mode:
authorYao Qi <yao@codesourcery.com>2014-04-22 12:56:08 +0800
committerYao Qi <yao@codesourcery.com>2014-05-16 20:19:00 +0800
commit95c64f92be44781ab0f9472e88296fbf971c79fa (patch)
tree2076c399f57d57df9dbfe633e25976daff209cbb /symlink-tree
parent19679ecafced89bcaea535d8129f6ecbc8199e9e (diff)
downloadgdb-95c64f92be44781ab0f9472e88296fbf971c79fa.zip
gdb-95c64f92be44781ab0f9472e88296fbf971c79fa.tar.gz
gdb-95c64f92be44781ab0f9472e88296fbf971c79fa.tar.bz2
Fix display of tabulation character for mingw hosts.
Pierre proposed this patch https://sourceware.org/ml/gdb-patches/2013-10/msg00011.html and Tom gave a suggestion that it's better to do check \t in print_wchar <https://sourceware.org/ml/gdb-patches/2013-11/msg00148.html> However, I don't see the follow-up to this discussion. We encounter two fails in printcmds.exp on mingw host, and Pierre's patch fixes them. I pick it up, update a little per Tom's comments, and post it here for review. This patch fixes these fails below on mingw32 host. FAIL: gdb.base/charset.exp: print string in ASCII FAIL: gdb.base/charset.exp: try printing '\t' in ASCII FAIL: gdb.base/charset.exp: print string in ISO-8859-1 FAIL: gdb.base/charset.exp: try printing '\t' in ISO-8859-1 FAIL: gdb.base/charset.exp: print string in UTF-32 FAIL: gdb.base/charset.exp: try printing '\t' in UTF-32 FAIL: gdb.base/printcmds.exp: p ctable1[9] FAIL: gdb.base/printcmds.exp: p &ctable1[1*8] Also regression tested on x86_64-linux. Is it OK? gdb: 2014-05-16 Pierre Muller <muller@sourceware.org> Yao Qi <yao@codesourcery.com> * valprint.c (print_wchar): Move the code on checking whether W is a printable wide char to the default branch of switch statement below. Call wchar_printable instead of gdb_iswprint.
Diffstat (limited to 'symlink-tree')
0 files changed, 0 insertions, 0 deletions