public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "wengxt at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sources.redhat.com
Subject: [Bug libc/13439] iconv and Qt work inproperly
Date: Sun, 18 Dec 2011 07:00:00 -0000	[thread overview]
Message-ID: <bug-13439-131-SfpRb2fwZ9@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-13439-131@http.sourceware.org/bugzilla/>

http://sourceware.org/bugzilla/show_bug.cgi?id=13439

--- Comment #5 from Weng Xuetian <wengxt at gmail dot com> 2011-12-18 06:59:50 UTC ---
Is it supposed to like this? The code use iconv_open TWICE.

I support each of iconv_t have it's own state, but not affect each other, this
is not true any more? As you can see, it's true in 2.13.

If it's not true, it will break many library. Like I just use
iconv_open("UTF-16", "UTF-8") here, and another library use
iconv_open("UTF-16", "UTF-8") in another place, but I didn't aware, then it
will break.

-- 
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.


  parent reply	other threads:[~2011-12-18  7:00 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-25 17:10 [Bug libc/13439] New: " wengxt at gmail dot com
2011-11-25 19:15 ` [Bug libc/13439] " aj at suse dot de
2011-11-25 21:31 ` wengxt at gmail dot com
2011-11-28  8:59 ` aj at suse dot de
2011-12-18  2:11 ` drepper.fsp at gmail dot com
2011-12-18  7:00 ` wengxt at gmail dot com [this message]
2011-12-21 23:48 ` drepper.fsp at gmail dot com
2014-02-16 18:24 ` jackie.rosen at hushmail dot com
2014-05-28 19:43 ` schwab at sourceware dot org
2014-06-13 14:24 ` fweimer at redhat dot com
2014-06-13 14:37 ` [Bug libc/13439] iconv_open incorrectly shares internal conversion state fweimer at redhat dot com

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=bug-13439-131-SfpRb2fwZ9@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=glibc-bugs@sources.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).