vector.com|Contact
Search tips

apple banana
Find rows that contain at least one of the two words.

+apple +juice
Find rows that contain both words.

+apple macintosh
Find rows that contain the word 'apple', but rank rows higher if they also contain 'macintosh'.

+apple -macintosh
Find rows that contain the word 'apple' but not 'macintosh'.

+apple ~macintosh
Find rows that contain the word 'apple', but if the row also contains the word 'macintosh', rate it lower than if row does not. This is "softer" than a search for '+apple -macintosh', for which the presence of 'macintosh' causes the row not to be returned at all.

+apple +(>turnover >strudel)
Find rows that contain the words 'apple' and 'turnover', or 'apple' and 'strudel' (in any order), but rank 'apple turnover' higher than 'apple strudel'.

apple*
Find rows that contain words such as 'apple', 'apples', 'applesauce', or 'applet'.

"some words"
Find rows that contain the exact phrase 'some words' (for example, rows that contain 'some words of wisdom' but not "some noise words").

By continuing to use this site you agree to the use of cookies. For more information and to find out how to change this click here. Accept Cookies
Please enable cookies in your browser for this website.
Search:
Advanced search

Probe Point at End of Function

Last updated: 2019-11-04

VectorCAST version 2019 SP2 now supports probe points at the end of functions, inserted right before each exit point. Specifically, if the function is void(), then the probe point is executed at the end of execution. If the function has one or more return() calls, then the probe point executes before the return() call and therefore before any function that might be called in the return() function. A function exit probe point is useful for calling VCAST_DUMP_COVERAGE_DATA() in a cover environment.

In the following example a function probe point is selected for the PlaceOrder function. The edit box for the function probe shows both entry and exit boxes.
 

 


 
  

Probe point files have changed as well.

Function entry probe points are now written in the following syntax in the probe point file, using PROBE_LOCATION: FUNCTION instead of PROBE_LOCATION:

--

BEGINNING_OF_FUNCTION:
 

PROBE_LOCATION: FUNCTION
PROBE_FUNCTION: my_function
PROBE_CODE:
vcast_probe_print("*** BEGINNING OF FUNCTION ***\n");
END_PROBE_CODE:

Function exit probe points are written with similar syntax:

PROBE_LOCATION: FUNCTION
PROBE_FUNCTION: my_function
PROBE_CODE_AFTER:
vcast_probe_print("*** END OF FUNCTION ***\n");
END_PROBE_CODE_AFTER:

 

The difference between the two is PROBE_CODE for entry point probes and PROBE_CODE_AFTER for exit point probes.

The probe point report has changed slightly. Accessed by selecting Probe Point Listing from the probe point icon on the toolbar, this report displays (function) instead of (beginning of function). In the report, text under Code Before is a function entry probe and Code After is in a function exit probe point.

 
Article Options
2019-11-04
Views: 7
Rate this article: