Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Roland Schwingel <roland.schwingel@onevision.de>
To: tromey@redhat.com
Cc: gdb <gdb@sourceware.org>
Subject: Re: Problem on cygwin with new wchar_t printing support via iconv()
Date: Wed, 25 Mar 2009 08:56:00 -0000	[thread overview]
Message-ID: <49C9F1EE.4020404@onevision.de> (raw)

Hi Tom,

Thanks for your reply...

Tom Tromey <tromey@redhat.com> wrote on 24.03.2009 17:44:20:

 > >>>>> "Roland" == Roland Schwingel <roland.schwingel@onevision.de> 
writes:
 >
 > Roland> I simply freezes when I try to step into a function having a
 > Roland> wchar_t * as parameter.  I have buildt gdb both using the
 > Roland> cygwin supplied libiconv and an own libiconv intree with gdb
 > Roland> sources.
 >
 > What version of libiconv are you using?
My cygwin 1.5.25 installation comes with libiconv 1.11. For my gdb
intree tests I used libiconv 1.12.

 > If you have a small test case, I will try to reproduce it with a
 > libiconv-based build here.  I suspect, though, that it is
 > Windows-specific.
 >
 > If you have dejagnu installed, you could try:
 >
 >     cd build/gdb
 >     make check RUNTESTFLAGS=charset.exp
 >
 > This works for me with a libiconv-based build (on x86 Fedora 9).

This test was done with the intree libiconv 1.12:

make[1]: Entering directory 
`/vol/d/compile/gdb-6.8.50-cvs-ov_obj/gdb/testsuite'
Nothing to be done for all...
Making a new config file...
rootme=`pwd`; export rootme; \
        srcdir=../../../gdb-6.8.50-cvs-ov/gdb/testsuite ; export srcdir ; \
        EXPECT=`if [ -f ${rootme}/../../expect/expect ] ; then echo 
${rootme}/../../expect/expect ; else echo expect ; fi` ; export EXPECT ; \
        EXEEXT=.exe ; export EXEEXT ; \
        
LD_LIBRARY_PATH=$rootme/../../expect:$rootme/../../libstdc++:$rootme/../../tk/unix:$rootme/../../tcl/unix:$rootme/../../bfd:$rootme/../../opcodes:$LD_LIBRARY_PATH; 
\
        export LD_LIBRARY_PATH; \
        if [ -f ${rootme}/../../expect/expect ] ; then  \
          TCL_LIBRARY=${srcdir}/../../tcl/library ; \
          export TCL_LIBRARY ; fi ; \
        runtest charset.exp
WARNING: Couldn't find the global config file.
Test Run By roland on Wed Mar 25 09:36:08 2009
Native configuration is i686-pc-cygwin

                === gdb tests ===

Schedule of variations:
    unix

Running target unix
Using /usr/share/dejagnu/baseboards/unix.exp as board description file 
for target.
Using /usr/share/dejagnu/config/unix.exp as generic interface file for 
target.
Using ../../../gdb-6.8.50-cvs-ov/gdb/testsuite/config/unix.exp as 
tool-and-target-specific interface file.
Running ../../../gdb-6.8.50-cvs-ov/gdb/testsuite/gdb.base/charset.exp ...
FAIL: gdb.base/charset.exp: print string in ISO-8859-1
FAIL: gdb.base/charset.exp: print string in EBCDIC-US
FAIL: gdb.base/charset.exp: check value of parsed character literal in 
EBCDIC-US
FAIL: gdb.base/charset.exp: check value of parsed string literal in 
EBCDIC-US
FAIL: gdb.base/charset.exp: try printing '\a' in EBCDIC-US
FAIL: gdb.base/charset.exp: check value of '\a' in EBCDIC-US
FAIL: gdb.base/charset.exp: check value of "\a" in EBCDIC-US
FAIL: gdb.base/charset.exp: try printing '\b' in EBCDIC-US
FAIL: gdb.base/charset.exp: check value of '\b' in EBCDIC-US
FAIL: gdb.base/charset.exp: check value of "\b" in EBCDIC-US
FAIL: gdb.base/charset.exp: try printing '\n' in EBCDIC-US
FAIL: gdb.base/charset.exp: check value of '\n' in EBCDIC-US
FAIL: gdb.base/charset.exp: check value of "\n" in EBCDIC-US
FAIL: gdb.base/charset.exp: try printing '\t' in EBCDIC-US
FAIL: gdb.base/charset.exp: check value of '\t' in EBCDIC-US
FAIL: gdb.base/charset.exp: check value of "\t" in EBCDIC-US
FAIL: gdb.base/charset.exp: check value of escape that doesn't exist in 
EBCDIC-US
FAIL: gdb.base/charset.exp: print string in IBM1047
FAIL: gdb.base/charset.exp: check value of parsed character literal in 
IBM1047
FAIL: gdb.base/charset.exp: check value of parsed string literal in IBM1047
FAIL: gdb.base/charset.exp: try printing '\a' in IBM1047
FAIL: gdb.base/charset.exp: check value of '\a' in IBM1047
FAIL: gdb.base/charset.exp: check value of "\a" in IBM1047
FAIL: gdb.base/charset.exp: try printing '\b' in IBM1047
FAIL: gdb.base/charset.exp: check value of '\b' in IBM1047
FAIL: gdb.base/charset.exp: check value of "\b" in IBM1047
FAIL: gdb.base/charset.exp: try printing '\n' in IBM1047
FAIL: gdb.base/charset.exp: check value of '\n' in IBM1047
FAIL: gdb.base/charset.exp: check value of "\n" in IBM1047
FAIL: gdb.base/charset.exp: try printing '\t' in IBM1047
FAIL: gdb.base/charset.exp: check value of '\t' in IBM1047
FAIL: gdb.base/charset.exp: check value of "\t" in IBM1047
FAIL: gdb.base/charset.exp: check value of escape that doesn't exist in 
IBM1047
FAIL: gdb.base/charset.exp: print string in UCS-4
FAIL: gdb.base/charset.exp: parse character literal in UCS-4
FAIL: gdb.base/charset.exp: check value of parsed character literal in UCS-4
FAIL: gdb.base/charset.exp: check value of parsed string literal in UCS-4
FAIL: gdb.base/charset.exp: try printing '\a' in UCS-4
FAIL: gdb.base/charset.exp: check value of '\a' in UCS-4
FAIL: gdb.base/charset.exp: check value of "\a" in UCS-4
FAIL: gdb.base/charset.exp: try printing '\b' in UCS-4
FAIL: gdb.base/charset.exp: check value of '\b' in UCS-4
FAIL: gdb.base/charset.exp: check value of "\b" in UCS-4
FAIL: gdb.base/charset.exp: try printing '\f' in UCS-4
FAIL: gdb.base/charset.exp: check value of '\f' in UCS-4
FAIL: gdb.base/charset.exp: check value of "\f" in UCS-4
FAIL: gdb.base/charset.exp: try printing '\n' in UCS-4
FAIL: gdb.base/charset.exp: check value of '\n' in UCS-4
FAIL: gdb.base/charset.exp: check value of "\n" in UCS-4
FAIL: gdb.base/charset.exp: try printing '\r' in UCS-4
FAIL: gdb.base/charset.exp: check value of '\r' in UCS-4
FAIL: gdb.base/charset.exp: check value of "\r" in UCS-4
FAIL: gdb.base/charset.exp: try printing '\t' in UCS-4
FAIL: gdb.base/charset.exp: check value of '\t' in UCS-4
FAIL: gdb.base/charset.exp: check value of "\t" in UCS-4
FAIL: gdb.base/charset.exp: try printing '\v' in UCS-4
FAIL: gdb.base/charset.exp: check value of '\v' in UCS-4
FAIL: gdb.base/charset.exp: check value of "\v" in UCS-4
FAIL: gdb.base/charset.exp: print escape that doesn't exist in UCS-4
FAIL: gdb.base/charset.exp: check value of escape that doesn't exist in 
UCS-4
FAIL: gdb.base/charset.exp: non-representable target character
FAIL: gdb.base/charset.exp: print '\9'
FAIL: gdb.base/charset.exp: basic wide character

                === gdb Summary ===

# of expected passes            129
# of unexpected failures        63
/vol/d/compile/gdb-6.8.50-cvs-ov_obj/gdb/testsuite/../../gdb/gdb 
version  6.8.50.20090324-cvs -nw -nx

make[1]: *** [check] Error 1
make[1]: Leaving directory 
`/vol/d/compile/gdb-6.8.50-cvs-ov_obj/gdb/testsuite'
make: *** [check] Error 2

As you can see it fails (but does not hang)...

Roland


             reply	other threads:[~2009-03-25  8:56 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-25  8:56 Roland Schwingel [this message]
2009-03-25 15:13 ` Pedro Alves
2009-03-25 15:19   ` Pedro Alves
2009-03-25 19:17   ` Tom Tromey
2009-03-25 19:14 ` Tom Tromey
  -- strict thread matches above, loose matches on Subject: below --
2009-03-24 10:04 Roland Schwingel
2009-03-24 16:44 ` Tom Tromey

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=49C9F1EE.4020404@onevision.de \
    --to=roland.schwingel@onevision.de \
    --cc=gdb@sourceware.org \
    --cc=tromey@redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox