#177 Possible bugs found when using Xcode's analyzer

open
nobody
None
5
2014-07-11
2010-10-04
No

When running macam through Xcode 3.2.4's Build and Analyze function, Xcode found 119 possible problem areas. Here are some of the more worrisome ones found:

/Users/~/makestuff/macam-pure/cameras/PicoDriver.m:289:1 The Objective-C class 'PicoDriver', which is derived from class 'GenericDriver', defines the instance method 'decodeBufferProprietary:' whose return type is 'void'. A method with the same name (same selector) is also defined in class 'GenericDriver' and has a return type of 'BOOL'. These two types are incompatible, and may result in undefined behavior for clients of these classes

/Users/cwbetts/makestuff/macam-pure/cameras/OV519Driver.m:841:1 The Objective-C class 'OV519Driver', which is derived from class 'MyCameraDriver', defines the instance method 'dumpRegisters' whose return type is 'void'. A method with the same name (same selector) is also defined in class 'MyCameraDriver' and has a return type of 'int'. These two types are incompatible, and may result in undefined behavior for clients of these classes

/Users/cwbetts/makestuff/macam-pure/cameras/MR97311Driver.m:267:1 The Objective-C class 'MR97310Driver', which is derived from class 'GenericDriver', defines the instance method 'decodeBufferProprietary:' whose return type is 'void'. A method with the same name (same selector) is also defined in class 'GenericDriver' and has a return type of 'BOOL'. These two types are incompatible, and may result in undefined behavior for clients of these classes

/Users/cwbetts/makestuff/macam-pure/cameras/SPCA561ADriver.m:219:1 The Objective-C class 'SPCA561ADriver', which is derived from class 'SPCA5XXDriver', defines the instance method 'decodeBuffer:' whose return type is 'void'. A method with the same name (same selector) is also defined in class 'SPCA5XXDriver' and has a return type of 'BOOL'. These two types are incompatible, and may result in undefined behavior for clients of these classes

There are also a few (possible) memory leaks that it found, but I won't copy them down.

Discussion


Log in to post a comment.