public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "polacek at redhat dot com" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sources.redhat.com Subject: [Bug stdio/13822] New: fmemopen cannot handle wide chars Date: Thu, 08 Mar 2012 09:11:00 -0000 [thread overview] Message-ID: <bug-13822-131@http.sourceware.org/bugzilla/> (raw) http://sourceware.org/bugzilla/show_bug.cgi?id=13822 Bug #: 13822 Summary: fmemopen cannot handle wide chars Product: glibc Version: unspecified Status: NEW Severity: normal Priority: P2 Component: stdio AssignedTo: unassigned@sourceware.org ReportedBy: polacek@redhat.com Classification: Unclassified Created attachment 6271 --> http://sourceware.org/bugzilla/attachment.cgi?id=6271 Testcase. Attached testcase segfaults with Fedora 16 glibc and trunk as well. The problem is that fgetws_unlocked calls _IO_getwline which is just return _IO_getwline_info (fp, buf, n, delim, extract_delim, (wint_t *) 0); however, in _IO_getwline_info is _IO_ssize_t len = (fp->_wide_data->_IO_read_end - fp->_wide_data->_IO_read_ptr); whereas (gdb) p fp->_wide_data $6 = (struct _IO_wide_data *) 0x0 -- 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.
next reply other threads:[~2012-03-08 9:11 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-03-08 9:11 polacek at redhat dot com [this message] 2012-10-25 12:47 ` [Bug stdio/13822] " siddhesh at redhat dot com 2012-10-25 12:55 ` siddhesh at redhat dot com 2012-10-25 13:11 ` polacek at redhat dot com 2012-10-25 13:21 ` siddhesh at redhat dot com 2012-10-25 18:12 ` bugdal at aerifal dot cx 2014-06-26 14:01 ` 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-13822-131@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: linkBe 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).