public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "Petr dot Salinger at seznam dot cz" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sources.redhat.com Subject: [Bug libc/2337] libio in wide mode deallocates user supplied buffer Date: Thu, 02 Mar 2006 14:07:00 -0000 [thread overview] Message-ID: <20060302140653.22472.qmail@sourceware.org> (raw) In-Reply-To: <20060214170527.2337.Petr.Salinger@seznam.cz> ------- Additional Comments From Petr dot Salinger at seznam dot cz 2006-03-02 14:06 ------- Bug 2337 - libio in wide mode deallocates user supplied buffer, same behaviour also for post 2.3.91 CVS snapshot Attached code snippet compiled with -DUSER_BUF still segfaults, can also be used for testsuite. Petr -- What |Removed |Added ---------------------------------------------------------------------------- Summary|libio in wide mode |libio in wide mode |deallocates user supplied |deallocates user supplied |buffer |buffer http://sourceware.org/bugzilla/show_bug.cgi?id=2337 ------- 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:[~2006-03-02 14:07 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2006-02-14 17:05 [Bug libc/2337] New: " Petr dot Salinger at seznam dot cz 2006-02-14 17:07 ` [Bug libc/2337] " Petr dot Salinger at seznam dot cz 2006-03-02 14:07 ` Petr dot Salinger at seznam dot cz [this message] 2006-05-03 11:30 ` Petr dot Salinger at seznam dot cz 2006-10-04 16:46 ` rsa at us dot ibm dot com 2006-10-04 19:55 ` rsa at us dot ibm dot com 2006-10-06 6:00 ` rsa at us dot ibm dot com 2006-10-06 17:10 ` rsa at us dot ibm dot com 2006-12-13 23:18 ` drepper at redhat dot com 2007-01-12 17:26 ` cvs-commit at gcc dot gnu dot org
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=20060302140653.22472.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: 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).