Object Subclass Tracking via Code Annotations
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In complex software environments, it is inefficient to determine the subset of operations performed on specific subclasses of objects due to the complexity of the system, making it difficult to track and analyze operations through code examination.
Innovation Solution
A debugging tool with an object subclass tracking module identifies and tracks subclasses of objects and their operations by using code annotations to generate unique IDs from stack traces, storing this information in object tracking tables for later debugging purposes, allowing for efficient analysis and debugging of kernel objects.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Measurement precision
If code examination is used to determine operations on object subclasses, then completeness of analysis is improved, but time consumption and complexity increase significantly
Solution Approach 1:
The patent applies preliminary action by pre-computing and storing subclass identification information and operation metadata during object creation and operation execution. Instead of examining code at analysis time, the system prepares tracking data in advance through code annotations that capture subclass IDs and operation details, making the analysis phase instantaneous while maintaining complete operation tracking
Solution Approach 2:
The patent uses copying by creating simplified representations of operation data through code annotations. Rather than analyzing the actual complex code structure, the system creates lightweight annotation copies that contain essential information (subclass ID, operation type, location), enabling fast analysis while preserving the completeness of operation tracking
2Measurement precision
If code examination is used to determine operations on object subclasses, then accuracy of tracking is improved, but system complexity increases
Solution Approach 1:
The patent introduces an intermediary mechanism through code annotations that act as mediators between the complex object subsystem and the tracking system. These annotations serve as simplified interfaces that capture essential tracking information without requiring direct analysis of complex code structures, thereby maintaining tracking accuracy while reducing system complexity
Solution Approach 2:
The patent applies segmentation by dividing the tracking system into distinct components: code annotations for data capture, subclass identification module for processing, and operation tracking module for recording. This segmentation allows each component to handle specific tasks independently, reducing overall system complexity while maintaining accurate tracking through specialized processing
3Reliability
If detailed tracking information is stored for all objects, then debugging capability is improved, but memory space consumption increases
Solution Approach 1:
The patent applies local quality by storing detailed tracking information selectively rather than uniformly for all objects. Code annotations are applied only to specific locations where subclass identification and operation tracking are needed, allowing detailed debugging information to be stored locally at relevant points while avoiding unnecessary memory consumption in other parts of the system
Data Source
AI summary
A mechanism for tracking subclasses of and operations performed by generic objects in a computer system is disclosed. A method of the disclosure includes receiving, by a debugging tool executed from a processing device, an invocation from a code annotation in a function executed by the processing device, the invocation to initialize an object subclass tracking module of the debugging tool, requesting a stack trace of a call stack of the function, generating an identification (ID) using the requested stack trace, and storing the generated ID and the stack trace in a new entry in an object tracking table.