Improvements to static analysis in GCC 14

Re:Improvements to static analysis in GCC 14 by jjav on Thursday April 04, 2024 @02:33AM (#39927197)

How is this useful though? I mean yes, it is useful in avoiding the buffer overruns. But that's not the only consideration, you also want code that handles data correctly. This just truncates at buffer size so data is lost.

So, if you want the code to work correctly, you need to either check the return code and reallocate dst and call the copy again. But if you're going to do that might as well check src len and allocate dst correctly before calling it so it never fails. But if you're already doing that, you can call strcpy just fine and never have a problem.

[ Parent | on HN ]

Re:Improvements to static analysis in GCC 14 by jandrese on Thursday April 04, 2024 @10:36AM (#39930979)

Sometimes truncation is fine or at least can be managed. Yes, strdup() is a better choice in a lot of situations, but depending on how your data is structured it may not be the correct option. I would say my version is useful in any situation where you were previously using strncpy/cat or strlcpy/cat.

[ Parent | on HN ]