The following operators can be used to better focus your queries.
( ) , AND, OR, NOT, W/#
? single char wildcard, not at start
* multi char wildcard, not at start
(Cat? OR feline) AND NOT dog?
Cat? W/5 behavior
(Cat? OR feline) AND traits
Cat AND charact*
This guide provides a more detailed description of the syntax that is supported along with examples.
This search box also supports the look-up of an IP.com Digital Signature (also referred to as Fingerprint); enter the 72-, 48-, or 32-character code to retrieve details of the associated file or submission.
Concept Search - What can I type?
For a concept search, you can enter phrases, sentences, or full paragraphs in English. For example, copy and paste the abstract of a patent application or paragraphs from an article.
Concept search eliminates the need for complex Boolean syntax to inform retrieval. Our Semantic Gist engine uses advanced cognitive semantic analysis to extract the meaning of data. This reduces the chances of missing valuable information, that may result from traditional keyword searching.
Call stack sampling using entry/exit events to maintain call stacks by thread for instrumented code
English (United States)
This text was extracted from a PDF file.
This is the abbreviated version, containing approximately
76% of the total text.
Page 1 of 1
Sampling and using entry/exit events to maintain call stacks by thread
Disclosed is a method for maintaining and utilizing thread based call stack information for code that is instrumented for entry/exit events. Dynamic instrumentation or recompilation with compiler options may be used to generate entry/exit events. See the hookit documentation at http://perfinsp.sourceforge.net/hookit.html for an example using compiler options.
One common approach is for profilers to maintain information in a tree for each entry/exit event. Instead thread based call stacks are maintained for each monitored thread by pushing the entry event information onto a stack in memory and popping the information off the stack when the exit event occurs. Specific conditions may be monitored, such as, the number of instructions between two events or the number of bytes allocated by monitoring object allocation events. When the monitored conditions occur, the maintained calling sequence can be used to walk the information into a thread based call tree where a counter in the leaf node of the tree is incremented to indicate a sample occurred. Reports may be generated that give information similar to reports generated by producing call trees for all method entry/exit events with less overhead. This approach may also be used for time based sampling to produce reports.
The overhead of the entry/exit events is significant, but the methodology of maintaining...