Searched full:safe (Results 1 – 25 of 42) sorted by relevance
12
5 memory safe and have no side effects relevant to the memory safety of15 call of FreeRTOS_ARP.c is memory safe.22 of FreeRTOS_ARP.c is memory safe.25 that the code is not memory safe, if the allocation
1 FreeRTOS_PrintARPCache_harness.c is memory safe,2 assuming vLoggingPrintf is correct and memory safe.
3 The ARPSendGratutious function is memory safe,4 if xQueueGenericSend is memory safe.
30 /* This function has been proved to be memory safe in another proof (in ARP/ARPRefreshCacheEntry). …37 /* This function has been proved to be memory safe in another proof (in ARP/ARPProcessPacket). Henc…47 /* This function has been proved to be memory safe in another proof (in parsing/ProcessIPPacket). H…
1 Assuming that xNetworkInterfaceOutput is memory safe,
1 ARPGetCacheEntryByMac is memory safe,
2 ARPProcessPacket is memory safe independent
2 ARPRefreshCacheEntry is memory safe independent
2 is memory safe for all possible combinations of ipconfigARP_STORES_REMOTE_ADDRESSES
5 memory safe and have no side effects relevant to the memory safety of
6 memory safe and have no side effects relevant to the memory safety of
3 description: "Thread safe FreeRTOS TCP/IP stack working on top of the FreeRTOS-Kernel to implement …
61 operation is safe to perform in that case, as we are using a generic API143 safe to suppress.
13 memory safe and have no side effects relevant to the memory safety of
5 /* Implementation of safe malloc which returns NULL if the requested size is 0.
31 * DNS_ParseDNSReply proved memory safe elsewhere41 * Abstract DNS_ParseDNSReply proved memory safe in ParseDNSReply.
60 /* The application provides the random number and time hook in a memory safe manner. */ in harness()
71 /* Implementation of safe malloc */
119 /* Non-format version thread-safe print. */122 /* Non-format version thread-safe print. */
50 * DNS_ParseDNSReply proved memory safe elsewhere60 * Abstract DNS_ParseDNSReply proved memory safe in ParseDNSReply.
