On Tuesday 2021-05-18 10:45, Simon Lees wrote:
The warning means, that the library exists the program at an error instead of returning an error code to the calling binary. This is considered as bad practice, but has to be fixed upstream. So you can ignore it.
OK, thank You, submitted to OBS, I'm going to report it upstream. :-)
Its also worth noting that in some cases upstream has a really good reason for this (or the error is incorrect) and in such cases you can continue to ignore the warning (this is why its a warning not an error).
Unless a library uses fork() to make some new processes, I can't really see an excuse for "exit". At minimum, that should be an abort. Or, since it's a C++ code section, "throw" (which counts towards the proper implementation of "error code").