| Allegro CL version 10.1 The object described on this page has been modified in the 10.1 release; see the Release Notes. 10.0 version | ||||||||||
Arguments: &key verbose profile current-profile
This function will print to *standard-output* the status of the current data
collection. If the runtime analysis was invoked with the with-profiling macro, the form
to be analyzed is also printed.
This function returns one of the following possible values:
- :inactive -- data collection has not yet started
- :suspended -- data collection has started, but sampling is currently not being done
- :sampling -- data collection has been started and sampling is occurring
- :saved -- data collection has stopped, but as yet no analysis of saved data has occurred
- :analyzed -- all data of a finished profile has been analyzed
The profile keyword
argument specifies the profile to examine. Its value must be a
name of a profile (see save-named-profile) or a profile object (see
find-named-profile). The
value :current is also accepted and is the
default. It indicates the current profile (the most recent run and
stopped but not saved and named profile).
Use of the current-profile keyword argument is deprecated and will cause a warning to be signaled. Use profile instead. If supplied, its value must be a profile saved by save-named-profile or the name of such a profile (see find-named-profile). Profiles saved by the deprecated function save-current-profile will also work).
The verbose keyword argument, if
true (default is t),
causes additional information about runtime analysis to be printed. If
you specify it as nil, only the appropriate
keyword (from the list above) is returned and nothing additional is
printed.
A finalized analysis (profiler-status returns
:analyzed) can be saved using
save-named-profile.
See runtime-analyzer.htm for general information on the runtime analyzer.
Copyright (c) 1998-2022, Franz Inc. Lafayette, CA., USA. All rights reserved.
This page was not revised from the 10.0 page.
Created 2019.8.20.
| Allegro CL version 10.1 The object described on this page has been modified in the 10.1 release; see the Release Notes. 10.0 version | ||||||||||