https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94849
Martin Liška <marxin at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |ASSIGNED
Assignee|unassigned at gcc dot gnu.org |marxin at gcc dot
gnu.org
Ever confirmed|0 |1
Last reconfirmed| |2020-04-29
--- Comment #1 from Martin Liška <marxin at gcc dot gnu.org> ---
(In reply to Rachel Mant from comment #0)
> Created attachment 48408 [details]
> A simple fix for the bug
>
> fopen() (actually fopen64 because of macro remapping) as implemented by
> Glibc and other C run-times allows the first "path" or "filename" parameter
> to be nullptr and causes the function to simply do nothing and return
> nullptr itself when this happens.
>
Thank you for the report. Can you please find where is the behavior documented?
I can't find anything about NULL pointer argument at:
man fopen.
