From: Tom Tromey <tromey@redhat.com>
To: Roland Schwingel <roland.schwingel@onevision.de>
Cc: gdb <gdb@sourceware.org>
Subject: Re: Problem on cygwin with new wchar_t printing support via iconv()
Date: Wed, 25 Mar 2009 19:14:00 -0000 [thread overview]
Message-ID: <m3k56dza7u.fsf@fleche.redhat.com> (raw)
In-Reply-To: <49C9F1EE.4020404@onevision.de> (Roland Schwingel's message of "Wed\, 25 Mar 2009 09\:57\:18 +0100")
>>>>> "Roland" == Roland Schwingel <roland.schwingel@onevision.de> writes:
Roland> My cygwin 1.5.25 installation comes with libiconv 1.11. For my gdb
Roland> intree tests I used libiconv 1.12.
Actually, it occurred to me today that the in-tree libiconv is only
used if there is no iconv already available. So, I think even in this
case gdb is picking up the cygwin libiconv.
Could you try a simple test? Run gdb on your program, evaluate
'set target-wide-charset UCS-2', and then 'print L"abcd"'.
Does that work? Or hang?
If it works, can you make it hang with some other string?
Or do you know the contents of the wchar_t* in the backtrace that
makes it hang?
Also, I can tell you how to hack gdb's configure to really try
libiconv 1.12. That would determine whether we are seeing a libiconv
bug. Would you mind trying this?
Tom
next prev parent reply other threads:[~2009-03-25 19:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-25 8:56 Roland Schwingel
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 [this message]
-- 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=m3k56dza7u.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=gdb@sourceware.org \
--cc=roland.schwingel@onevision.de \
/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