public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug libc/25895] New: Document fopen with pathname == NULL
@ 2020-04-29 14:52 marxin.liska at gmail dot com
  2020-04-29 15:26 ` [Bug libc/25895] " schwab@linux-m68k.org
                   ` (6 more replies)
  0 siblings, 7 replies; 8+ messages in thread
From: marxin.liska at gmail dot com @ 2020-04-29 14:52 UTC (permalink / raw)
  To: glibc-bugs

https://sourceware.org/bugzilla/show_bug.cgi?id=25895

            Bug ID: 25895
           Summary: Document fopen with pathname == NULL
           Product: glibc
           Version: unspecified
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: libc
          Assignee: unassigned at sourceware dot org
          Reporter: marxin.liska at gmail dot com
                CC: drepper.fsp at gmail dot com
  Target Milestone: ---

It's follow up of:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94849

There are 2 questions:
- is it valid to call fopen with pathname == NULL?
- NULL argument is not mentioned at 'man fopen'

Note that Microsoft allows NULL argument:
https://docs.microsoft.com/en-us/cpp/c-runtime-library/reference/fopen-wfopen?view=vs-2019

-- 
You are receiving this mail because:
You are on the CC list for the bug.

^ permalink raw reply	[flat|nested] 8+ messages in thread

end of thread, other threads:[~2024-05-10  1:56 UTC | newest]

Thread overview: 8+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2020-04-29 14:52 [Bug libc/25895] New: Document fopen with pathname == NULL marxin.liska at gmail dot com
2020-04-29 15:26 ` [Bug libc/25895] " schwab@linux-m68k.org
2020-04-29 16:37 ` marxin.liska at gmail dot com
2020-05-04 18:11 ` marxin.liska at gmail dot com
2020-05-09  8:02 ` mliska at suse dot cz
2024-04-18 15:52 ` [Bug libc/25895] Add __nonnull ((1)) to fopen declaration carlos at redhat dot com
2024-04-18 15:53 ` carlos at redhat dot com
2024-05-10  1:56 ` sam at gentoo dot org

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).