Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: "Pierre Muller" <pierre.muller@ics-cnrs.unistra.fr>
To: "'gdb'" <gdb@sourceware.org>
Subject: Problems with recent GDB Cygwin builds
Date: Fri, 15 Apr 2011 10:34:00 -0000	[thread overview]
Message-ID: <002601cbfb58$a52dff20$ef89fd60$@muller@ics-cnrs.unistra.fr> (raw)

Using recent Cygwin builds, either trunk or 7.3 branch,
I do get problems with iconv DLL.

  Typically, all string display fail.

Easiest way to check is 
compile new TRUNK gdb
go to build/gdb dir
prompt# ./gdb ./gdb

...
(top-gdb) print version
$1 =
(top-gdb)

while

prompt# ./gdb ./gdb

...
(top-gdb) p version
$1 = "7.2.90.20110414-cvs"
(top-gdb)

  Trying to debug this, I clearly see that iconv callsdo fail
iconv is a macro and really calls libiconv which is in cygiconv-2.dll
as $eax=-1 on return.

$ cygcheck.exe -s |grep iconv
  980k 2011/01/28 E:\cygwin-1.7\bin\cygiconv-2.dll
libiconv                       1.13.1-2            OK
libiconv2                      1.13.1-2            OK


  The problem seems to be that wchar_iterate returns 2 while
the expected result is 0 or 1.

  Mingw32 or mingw64 seem to work just fine.

Does anyone else have the same kind of troubles?

Pierre Muller.

PS: I tried to compile libiconv-1.13.1-2 but it seems to require me to
install
lots of stuff I don't have ...



             reply	other threads:[~2011-04-15 10:34 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-15 10:34 Pierre Muller [this message]
2011-04-15 13:29 ` Pierre Muller
     [not found] ` <15303.5644245849$1302874163@news.gmane.org>
2011-04-15 15:38   ` Tom Tromey
2011-04-15 15:59     ` Pierre Muller

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='002601cbfb58$a52dff20$ef89fd60$@muller@ics-cnrs.unistra.fr' \
    --to=pierre.muller@ics-cnrs.unistra.fr \
    --cc=gdb@sourceware.org \
    /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