Error list and bug report analysis for configuring an application tracer
View Patent ↗Error logs, bug reports, and other databases identifying problems with a tracer system may be mined to determine how a tracer may interact with a given function, module, or other group of functions. Based on such reports, a tracer may be configured to avoid certain functions or to trace such functions in a specific manner. In some cases, tracer may be configured to limit tracing to certain parameters or with other limitations to avoid any known conditions under which errors occur.
1. A method performed by at least one computer processor, said method comprising:
searching an error database to identify a first error related to tracing a first function, said first function being called during execution of an application with a tracer;
updating a tracer list with an entry related to said first function, said tracer list being referenced by said tracer during execution of said application with said tracer;
said entry identifying said first function and causing said tracer to not trace said first function based on said entry.
2. The method of claim 1 , said entry comprising a first condition under which said first function is not to be traced.
3. The method of claim 2 , said first condition being derived from metadata associated with said first error.
4. The method of claim 3 , said metadata comprising a second function being called as part of said application.
5. The method of claim 3 , said metadata comprising a software configuration under which said first error occurred.
6. The method of claim 3 , said metadata comprising a hardware configuration under which said first error occurred.
7. The method of claim 3 , said first error being identified by said tracer.
8. The method of claim 7 , said first error being added to said error database by said tracer.
9. The method of claim 3 , said first error being identified by a user, said first error being added to said error database by at least one user action.
10. The method of claim 1 , said tracer list being updated during said execution of said application with said tracer.
11. The method of claim 1 , said error database comprising errors gathered during tracing a plurality of applications.
12. The method of claim 11 , said first error being encountered during execution of a second application with said tracer.
13. A system comprising:
at least one processor;
a tracer list manager executing on said at least one processor, said tracer list manager that:
searches an error database and identifies a first error related to tracing a first function, said first function being called during execution of an application with a tracer;
updates a tracer list with an entry related to said first function, said tracer list being referenced by said tracer during execution of said application with said tracer;
said entry identifying said first function and causing said tracer to not trace said first function based on said entry.
14. The system of claim 13 , said error database comprising errors gathered from a plurality of tracer runs.
15. The system of claim 14 , said error database comprising errors gathered from a plurality of tracer runs performed on a plurality of different applications.
16. The system of claim 15 , said first error occurring while tracing a second application.
17. The system of claim 13 , said entry comprising a first condition under which said first function is not to be traced.
18. The system of claim 17 , said tracer list defining a second condition under which said first function is to be traced.
19. The system of claim 13 , said first function being defined by a module name.