On 16/9/20 11:42 pm, Joel Sherrill wrote: > snprintf() is a safe method and I strongly disagree with the blanket > replacement > of many safe methods with memcpy(). > > Based on what POSIX profiles snprintf() is included in and the safety and > security requirements those profiles are designed to meet, snprintf() is > supported by RTOSes that can meet DO-178 Level A. > > If the POSIX method being reviewed is in the FACE Safety Base or Safety > Extended > profile, then it is OK to use and has been used in flight qualified > applications. And that is a general statement meaning running on any of a > variety of RTOSes. If the usage is incorrect, let's fix it but blanket > changing > them is wrong.
This is really good information, thank you. I see EPICS is reporting similar issues at the moment and looking to work around them. Is there a history of why this has been added to compilers as a warning? Chris _______________________________________________ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel
