All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marko Myllynen <myllynen-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
To: "Michael Kerrisk (man-pages)"
	<mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
	Peng Haitao <penght-BthXqXjhjHXQFUHtdCDX3A@public.gmane.org>
Cc: linux-man <linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
	Carlos O'Donell <carlos-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
Subject: Thread-safety of iconv()
Date: Mon, 15 Sep 2014 12:32:37 +0300	[thread overview]
Message-ID: <5416B235.8020309@redhat.com> (raw)

Hi Michael, Haitao,

iconv(3) states:

ATTRIBUTES
   Multithreading (see pthreads(7))
       The iconv() function is thread-safe.

But iconv_open(3) says:

A conversion descriptor contains a conversion  state.   After  creation
using iconv_open(), the state is in the initial state.  Using iconv(3)
modifies the descriptor's conversion state.  (This implies that a  con-
version descriptor can not be used in multiple threads simultaneously.)
To bring the state back to the initial state, use iconv(3) with NULL as
inbuf argument.

This looks a bit unclear, do you think you could clarify iconv(3) and/or
iconv_open(3) a bit in thread-safety regard?

Thanks,

-- 
Marko Myllynen
--
To unsubscribe from this list: send the line "unsubscribe linux-man" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

             reply	other threads:[~2014-09-15  9:32 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-15  9:32 Marko Myllynen [this message]
     [not found] ` <5416B235.8020309-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2014-09-18  6:50   ` Thread-safety of iconv() Peng Haitao
     [not found]     ` <541A80BD.8050509-BthXqXjhjHXQFUHtdCDX3A@public.gmane.org>
2014-09-18 13:14       ` Carlos O'Donell
     [not found]         ` <541ADAC1.2090108-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2014-09-19  2:57           ` Alexandre Oliva

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=5416B235.8020309@redhat.com \
    --to=myllynen-h+wxahxf7alqt0dzr+alfa@public.gmane.org \
    --cc=carlos-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
    --cc=linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
    --cc=penght-BthXqXjhjHXQFUHtdCDX3A@public.gmane.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.