[Bug sanitizer/80424] New: libasan uses tempnam tmpnam tmpnam_r
zeccav at gmail dot com
gcc-bugzilla@gcc.gnu.org
Fri Apr 14 06:33:00 GMT 2017
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80424
Bug ID: 80424
Summary: libasan uses tempnam tmpnam tmpnam_r
Product: gcc
Version: 7.0.1
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: sanitizer
Assignee: unassigned at gcc dot gnu.org
Reporter: zeccav at gmail dot com
CC: dodji at gcc dot gnu.org, dvyukov at gcc dot gnu.org,
jakub at gcc dot gnu.org, kcc at gcc dot gnu.org
Target Milestone: ---
Host: x86_64-pc-linux-gnu
Running make check on an address sanitized version of gcc trunk 246751
I get lots of the following:
/home/vitti/1tb/vitti/local/gcc-7-246751/lib64/libasan.so.4: warning: the use
of `tempnam' is dangerous, better use `mkstemp'
/home/vitti/1tb/vitti/local/gcc-7-246751/lib64/libasan.so.4: warning: the use
of `tmpnam' is dangerous, better use `mkstemp'
/home/vitti/1tb/vitti/local/gcc-7-246751/lib64/libasan.so.4: warning: the use
of `tmpnam_r' is dangerous, better use `mkstemp'
Is the address sanitizer using dangerous system calls?
Then they should be changed to mkstemp.
Otherwise is there a way to avoid those warnings?
Maybe setting a global variable?
More information about the Gcc-bugs
mailing list