public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "drepper at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sources.redhat.com
Subject: [Bug libc/10460] "iconv" corrupts all files over 17 KB from UTF8 to UTF16
Date: Sat, 01 Aug 2009 03:44:00 -0000 [thread overview]
Message-ID: <20090801034405.5996.qmail@sourceware.org> (raw)
In-Reply-To: <20090729181657.10460.murielle.descerisiers@gmail.com>
------- Additional Comments From drepper at redhat dot com 2009-08-01 03:44 -------
I cannot reproduce any problem. Neither on x86 nor x86-64. Not with glibc 2.8,
2.10, or the current development version. You didn't specify the architecture
so I don't know whether it's an alignment issue or just a broken binary on your
side. Such vague problems should always be reported to the distribution maker.
If you have concrete information on how you can reproduce the problem with the
current sources reopen the bug. Otherwise you're on your own. Particularly if
you're not using the latest code.
--
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution| |WORKSFORME
http://sourceware.org/bugzilla/show_bug.cgi?id=10460
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
next prev parent reply other threads:[~2009-08-01 3:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-29 18:17 [Bug libc/10460] New: " murielle dot descerisiers at gmail dot com
2009-07-29 18:18 ` [Bug libc/10460] " murielle dot descerisiers at gmail dot com
2009-08-01 3:44 ` drepper at redhat dot com [this message]
[not found] <bug-10460-131@http.sourceware.org/bugzilla/>
2013-07-06 15:41 ` krichter722 at aol dot de
2013-07-06 15:42 ` krichter722 at aol dot de
2013-07-07 3:25 ` bugdal at aerifal dot cx
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=20090801034405.5996.qmail@sourceware.org \
--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).