Surety is performing system maintenance this weekend. Electronic date stamps on new Prior Art Database disclosures may be delayed.
Browse Prior Art Database

Function call stack based application debugging

IP.com Disclosure Number: IPCOM000235880D
Publication Date: 2014-Mar-28
Document File: 2 page(s) / 20K

Publishing Venue

The IP.com Prior Art Database


During debugging it is often required to inspect a specific function being invoked. The interested function could be called frequently and from multiple places. In such cases, pipointing the condition at which user wants to collect debug infomraiton for such functions would be a challenge.

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 51% of the total text.

Page 01 of 2

Function call stack based application debugging

Disclosed in this article is a framework to provide user the capability of specifying debug/probe

points with function call stack information for finer control over debugging.

In today's infrastructure for static and dynamic debugging, there are facilities to inform the debugger to take the action when a specified function. Along with this specification users can

provide information such as for which process or arguments or line number in the function etc. These additional conditions equip users with some level of fine grained control over debugging. For example : User can specify whenever a line in a given function is invoked do some action, or whenever a system call is called for a given process do some action and etc.

Ease of using above mentioned examples to quickly get to the recreate state largely depends upon the number of times the line of function is executed, number of times the interested system call is called. In other words, frequency of occurrence of the specified condition is the driving factor. Since there is no restriction on when and how the user writes applications to invoke various functions, it may happen that the interested function is called from multiple places and we are looking at a specified invocation stack for the function. It is in such scenarios users will have a hard time getting to the recreate state of the issue they are trying to debug. If, recreate state or the interested point is reached quickly, users could spend more time in identifying the cause of the problem.

Proposed framework addresses any kind of debuggers example dynamic and static debuggers. With the proposed approach implemented, users will have an option to specify the function call stack details along with debug/probe point as a condition. With this, user will be able to instruct debugg...