[Bug 20775] Re: libc6's printf and fprintf don't return -1 on closed stdout/stderr.

Launchpad has imported 4 comments from the remote bug at http://sourceware.org/bugzilla/show_bug.cgi?id=1146. If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://hel

[Bug 20775] Re: libc6's printf and fprintf don't return -1 on closed stdout/stderr.

> Seems fixed in AMD64 7.10. closing. ** Changed in: glibc (Ubuntu) Status: Confirmed => Fix Released -- libc6's printf and fprintf don't return -1 on closed stdout/stderr. https://bugs.launchpad.net/bugs/20775 You received this bug notification because you are a member of Ubuntu Bugs,

Re: [Bug 20775] Re: libc6's printf and fprintf don't return -1 on closed stdout/stderr.

> Is this still an issue on gutsy and/or hardy? Seems fixed in AMD64 7.10. $ LINEBUF= ./closed 4>&1 <&- >&- 2>&- getchar=-1 puts=-1 printf=-1 fprintf=-1 fprintf=-1 $ ldd closed libc.so.6 => /lib/libc.so.6 (0x2b9d1e191000) /lib64/ld-linux-x8

[Bug 20775] Re: libc6's printf and fprintf don't return -1 on closed stdout/stderr.

Is this still an issue on gutsy and/or hardy? -- libc6's printf and fprintf don't return -1 on closed stdout/stderr. https://bugs.launchpad.net/bugs/20775 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu

[Bug 20775] Re: libc6's printf and fprintf don't return -1 on closed stdout/stderr.

Can this be put on the "Definite" list for Feisty + 1? If there are any programs that assume this behavior, we should be able to catch them by fixing it early on. -- libc6's printf and fprintf don't return -1 on closed stdout/stderr. https://bugs.launchpad.net/bugs/20775 You received this bug not

[Bug 20775] Re: libc6's printf and fprintf don't return -1 on closed stdout/stderr.

** Changed in: glibc (Ubuntu) Assignee: Jeff Bailey => (unassigned) -- libc6's printf and fprintf don't return -1 on closed stdout/stderr. https://bugs.launchpad.net/bugs/20775 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubun

[Bug 20775] Re: libc6's printf and fprintf don't return -1 on closed stdout/stderr.

Test case still fails on Feisty. -- libc6's printf and fprintf don't return -1 on closed stdout/stderr. https://launchpad.net/bugs/20775 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 20775] Re: libc6's printf and fprintf don't return -1 on closed stdout/stderr.

Same results as above obtained on Ubuntu 6.06. $ ldd closed linux-gate.so.1 => (0xe000) libc.so.6 => /lib/tls/libc.so.6 (0xb7e83000) /lib/ld-linux.so.2 (0xb7fbe000) $ dpkg -S /lib/tls/libc.so.6 libc6: /lib/tls/libc.so.6 $ apt-show-versions -

[Bug 20775] Re: libc6's printf and fprintf don't return -1 on closed stdout/stderr.

** Changed in: glibc (upstream) Status: Unknown => Fix Released -- libc6's printf and fprintf don't return -1 on closed stdout/stderr. https://launchpad.net/bugs/20775 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 20775] Re: libc6's printf and fprintf don't return -1 on closed stdout/stderr.

** Bug watch added: Sourceware.org Bugzilla #1146 http://sourceware.org/bugzilla/show_bug.cgi?id=1146 ** Also affects: glibc (upstream) via http://sourceware.org/bugzilla/show_bug.cgi?id=1146 Importance: Unknown Status: Unknown -- libc6's printf and fprintf don't return -1 on clo