On 13.12.2017 10:35, Josef Reidinger wrote:
How does coverity or other handle pointers in C++? I think it is similar kind of issue as ruby have for static analysis. Any pointer can be NULL or invalid address and similar in ruby anything can be nil.
Coverity will (among a lot of other things) complain if you use a pointer that you got e.g. as a function parameter and didn't check it first before dereferencing it. Sometimes this will result in false positives, but an extra check is cheap and can indeed prevent a segfault. Kind regards -- Stefan Hundhammer <shundhammer@suse.de> YaST Developer SUSE Linux GmbH GF: Felix Imendörffer, Jane Smithard, Graham Norton; HRB 21284 (AG Nürnberg) Maxfeldstr. 5, 90409 Nürnberg, Germany -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org To contact the owner, e-mail: yast-devel+owner@opensuse.org