Application Error Mapping for Third-Party Library Debugging
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing application error data is not effectively shared with third-party library developers, making it difficult for them to identify and address coding faults in library-dependent source code that cause application errors or crashes.
Innovation Solution
An application server system processes application error data to generate library error data, which is then sent to third-party library development systems, attributing errors to specific libraries based on mapping between library-dependent source code and application error data, and providing this information to facilitate code analysis.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If application error data is processed and shared with third-party library developers, then library quality and application stability improve, but data processing complexity and system complexity increase
Solution Approach 1:
The system segments application error data into library-specific error data by mapping library-dependent source code to third-party libraries. This segmentation allows targeted analysis of errors in specific libraries without processing all application errors, reducing overall processing complexity while improving reliability through focused library quality improvements.
Solution Approach 2:
The application server system acts as an intermediary between client computing devices and third-party library development systems. It receives application error data, processes and maps it to identify library-specific issues, then transmits relevant library error data to developers. This intermediary role distributes the complexity across multiple systems rather than concentrating all processing in one location.
2Measurement precision
If mapping data is used to attribute errors to specific libraries, then error attribution accuracy improves, but data processing time increases
Solution Approach 1:
Mapping data that links library-dependent source code to third-party libraries is prepared and stored in advance. When application error data is received, the system can immediately perform attribute mapping without time-consuming analysis, as the relationships between code and libraries are pre-established. This preliminary action enables accurate error attribution while minimizing real-time processing time.
3Reliability
If library error data is transmitted to third-party development systems, then library development quality improves, but information transmission overhead increases
Solution Approach 1:
The system extracts only the relevant portions of application error data that pertain to third-party libraries and transmits only this extracted library error data to development systems. By taking out and transmitting only the necessary information rather than all application error data, the system reduces information transmission overhead while still enabling library developers to improve quality effectively.
Data Source
AI summary
An example method includes receiving, by an application server system and from one or more client computing devices, application error data associated with at least one error that occurred during execution of at least one application, receiving mapping data that provides a mapping between (i) library-dependent source code of the application(s) and (ii) at least one third-party library from which the library-dependent source code is loaded during execution of the application(s), determining, based on the application error data and the mapping data, a match between the library-dependent source code and at least one portion of the application error data, attributing the at least one error to the at least one third-party library, generating library error data associated with the at least one third-party library, and sending, to at least one third-party library development system, the library error data.