From: Ulrich Drepper <drepper@redhat.com>
To: Jakub Jelinek <jakub@redhat.com>
Cc: Arjan van de Ven <arjan@linux.intel.com>,
Glibc hackers <libc-hacker@sources.redhat.com>
Subject: Re: [PATCH] Fix wide stdio
Date: Fri, 24 Nov 2006 15:17:00 -0000 [thread overview]
Message-ID: <45670D02.6010402@redhat.com> (raw)
In-Reply-To: <20061124130448.GK3849@sunsite.mff.cuni.cz>
Jakub Jelinek wrote:
> testcase from Arjan we attempt to munmap fp->_shortbuf (which is fortunately
> not page aligned and thus the munmap just fails).
No. We have this bug in the upstream BZ for some time and even had one
of the IBM people try to provide a patch. It's not that easy. The
current code is screwed up big time when it comes to wide streams and
setvbuf. It's not such a trivial change.
--
➧ Ulrich Drepper ➧ Red Hat, Inc. ➧ 444 Castro St ➧ Mountain View, CA â–
next prev parent reply other threads:[~2006-11-24 15:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-24 13:05 Jakub Jelinek
2006-11-24 15:17 ` Ulrich Drepper [this message]
2006-11-27 14:05 ` Jakub Jelinek
2006-11-27 15:13 ` Ulrich Drepper
2006-12-08 9:53 ` Jakub Jelinek
2006-12-13 23:20 ` Ulrich Drepper
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=45670D02.6010402@redhat.com \
--to=drepper@redhat.com \
--cc=arjan@linux.intel.com \
--cc=jakub@redhat.com \
--cc=libc-hacker@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).