On 2022-7-27 03:42 , Dave Allured - NOAA Affiliate via macports-dev wrote:
If you want to be thorough, then search the rest of the code for all references to this function. Look for any call that checks a return code. Also see if and how the function is defined for public or external use. If there is any hint of referencing a return code, then declare the return type as "int", and add return (0) at the end of the main part of the function.
Hopefully nothing is checking the return code, because there's a good chance that if it does it's reading uninitialised memory or the end of the previous stack frame (this is one of those "undefined behaviour" situations that C is (in)famous for.) But if it is, all the more reason to fix it…
- Josh
