Abstract: In embodiments of determining relevant events in source code analysis, a computing device includes a key event manager that is implemented to traverse executable paths in source code of executable software instructions, log events along the executable paths in the source code, and determine a defect in the source code along an executable path in the source code. A state machine is implemented to traverse back through the logged events and determine relevant events that are associated with the defect in the source code. An analysis output of the relevant events can then be generated to indicate the defect in the source code and a cause of the defect.

Abstract: The present invention provides a system, method and apparatus for automatically classifying voice communications, such as voice messages and phone calls in prerecorded voicemails (one speaker) and two-way conversations, as either spam or legitimate signals in a communications system (e.g., SIP, IMS, UMA, etc.). More specifically, the present invention classifies a voice communication session by receiving one or more voice communication packets associated with the voice communication session, extracting one or more properties from the received voice communication packets and classifying the voice communication session based on the extracted properties. The present invention can also be implemented as a computer program embodied on a computer readable medium wherein each step is performed by one or more code segments.

Abstract: In embodiments of determining relevant events in source code analysis, a computing device includes a key event manager that is implemented to traverse executable paths in source code of executable software instructions, log events along the executable paths in the source code, and determine a defect in the source code along an executable path in the source code. A state machine is implemented to traverse back through the logged events and determine relevant events that are associated with the defect in the source code. An analysis output of the relevant events can then be generated to indicate the defect in the source code and a cause of the defect.

Abstract: In embodiments of defective code warning resolution analysis, defective code warnings are received, such as code development warnings and/or code execution warnings. The defective code warnings can be grouped into warning groups according to properties of each defective code warning. Each instance of a defective code warning in a warning group can then be determined as one of fixed, suppressed, or ignored. Each instance of the defective code warning in the warning group is also aggregated based on each warning state of fixed, suppressed, or ignored.