tr24731

I'm trying to fix an undefined reference to memcpy_s() error. I've included string.h in my file and the memcpy() function works okay, and I've also tried including memory.h . I'm on x64 Windows 7 and using gcc 4.8.1 to compile. #include <stdlib.h> #include <stdio.h> #include <string.h> void doMemCopy(char* buf, size_t buf_size, char* in, int chr) { memcpy_s(buf, buf_size, in, chr); } memory for buf has been allocated in the main function, which calls doMemCpy(buf, 64, in, bytes) . in is a string read from standard input Exact error from cmd terminal: undefined reference to "memcpy_s" collect2

Since a quick Google search did not find anything, I will try to ask here (since many people involved in gcc/clang hang around here) - What is the status of __STDC_LIB_EXT1__ in gcc/clang? We are developing a cross platform applicataion and I wanted to use some of the safe bounds checking functions from <stdio.h> (which by miracle are available on Visual Studio 2017), but could not compile the code with Xcode 9.2. I assumed maybe the clang version Xcode uses is outdated, but gcc 6.3.0 on Ubuntu behaves the same. I am trying to use tmpnam_s with the following sample: #if defined(__STDC_LIB_EXT1

I'm trying to find which header to include for strerrorlen_s function from C11 standard under MSVC 2017 . I need it for allocating space for error message which to get with strerror_s . The code is the following: auto size = strerrorlen_s(errno) + 1; char* errorReason = (char*)alloca(size); strerror_s(errorReason, size, errno); std::ostringstream oss; oss << "Cannot open: " << fileName << " Reason: " << errorReason; throw std::runtime_error(oss.str()); In the documentation are the following words: As with all bounds-checked functions, strerror_s and strerrorlen_s are only guaranteed to be

I'm working on legacy code for Windows platform. When I compile the code in VS2013 , it give following warning: error C4996: ' fopen ': This function or variable may be unsafe. Consider using fopen_s instead. To disable deprecation, use _CRT_SECURE_NO_WARNINGS. See online help for details." And it will also give samiliar warning for sprintf . I understand sprintf_s is more safe than sprintf because of buffer overflow. But how can be fopen_s be more safe than fopen , there is no chance of buffer overflow because fopen doesn't accept an buffer. Can anyone provide an case fopen is unsafe, and