Automated Error Resolution via Debugger and Document Database

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current methods for resolving software application errors are time-consuming and unreliable, relying on manual keyword searches that yield inconsistent and untrustworthy results, with high dependency on user input and search accuracy.

Innovation Solution

A method and system for on-the-fly technical support that uses a debugger to read error messages, identify failed modules and stages, and automatically search a document database for matching error codes, providing relevant information and creating webcases for unresolved issues, thereby streamlining error resolution.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If manual keyword search is used to resolve errors, then user can access error information, but the process is time-consuming and yields inconsistent results

Engineering Contradiction:
Improveconsistency of error informationVSAvoidtime to resolve error
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The debugger automatically performs error resolution tasks without requiring manual user intervention. It self-generates search queries using error codes and module identifiers, automatically searches the document database, and presents results to the user, thereby eliminating the time-consuming manual searching process while ensuring consistent results through systematic automated procedures

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The system pre-structures the document database with organized error codes, module identifiers, and stage information before runtime. This preliminary organization enables the debugger to quickly retrieve relevant error information through structured queries rather than manual searching, reducing resolution time while maintaining consistency through pre-established data relationships

Inventive Principle:
Principle #10Preliminary action

2Ease of operation

If manual searching is performed to obtain error information, then user can access solutions, but the process requires multiple iterations of manual user input

Engineering Contradiction:
Improveease of error resolutionVSAvoidtime for manual input iterations
Core Design Contradiction:
Ease of operationVSLoss of time

Solution Approach 1:

The debugger automatically extracts error codes from error messages, identifies failed modules and stages, constructs search queries, and retrieves results without requiring multiple iterations of manual user input. This automation dramatically improves ease of operation while eliminating the time spent on repetitive manual searching and input operations

Inventive Principle:
Principle #25Self-service

3Loss of information

If keyword-based search is used, then error information can be retrieved, but there is high dependency on keywords selected by user

Engineering Contradiction:
Improvecompleteness of error informationVSAvoiddependency on user keyword selection
Core Design Contradiction:
Loss of informationVSEase of operation

Solution Approach 1:

The debugger automatically generates search queries using error codes and module identifiers extracted from the error message, eliminating dependency on user keyword selection. This ensures complete and accurate error information retrieval by using systematic, automated query generation based on structured error data rather than relying on user-chosen keywords

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The document database is pre-structured with error codes and module identifiers organized in a systematic manner before runtime. This preliminary structuring enables the debugger to retrieve complete error information through automated queries based on extracted error codes, eliminating the need for users to select appropriate keywords while ensuring information completeness

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentEP2936315B1On-the-fly technical support
Publication Date: 2019.02.06 XILINX INC
  • EP2936315B1 patent drawingFigure 1
  • EP2936315B1 patent drawingFigure 2
  • EP2936315B1 patent drawingFigure 3

AI summary

A method performed by an information handling system for on-the-fly technical support is described. In an exemplary method, an error message (402) is read to obtain an error code (323) therefrom. A project directory (413) is searched to obtain a report (414); where the report (414) indicates a failed module of a plurality of executable modules (321 ), and where the report (414) is associated with the error message (402). A source of an error is identified from the error message (402). A failed stage of the failed module is identified from the report (414). A case inquiry (415) for the error message (402) is prepared for searching a document (320) for resolution of the error, where the case inquiry (415) identifies the failed stage. A network is accessed, and the case inquiry is sent over the network.