The following terms are used in subsequent sections; it may be helpful to refer to these definitions.
-fasl
+ fasl
files are the object files produced
by The Lisp
+ The Lisp
kernel is a C program with a fair amount of
platform-specific assembly language code. Its basic job is to
@@ -1766,5 +1766,5 @@
files on different platforms; see
Table 3.1, âPlatform-specific filename conventionsâ. A heap
+ A heap
image is a file that can be quickly mapped into a
process's address space. Conceptually, it's not too different
@@ -1777,5 +1777,5 @@
standard full heap image files on different platforms; see
Table 3.1, âPlatform-specific filename conventionsâ. A bootstrapping image is a minimal
+ A bootstrapping image is a minimal
heap image used in the process of building Clozure CL itself. The
bootstrapping image contains just enough code to load the rest
@@ -1789,5 +1789,5 @@
as-yet-unsupported ones) has a uniquely named subdirectory of
-
+
TRACE {
-
+
CCL:*TRACE-LEVEL* [Variable]
Variable bound to the current nesting level during execution of before and after trace actions. The default printing actions use it to determine the amount of indentation.
-
+
CCL:*TRACE-MAX-INDENT* [Variable]
The default before and after print actions will not indent by more than the value of ccl:*trace-max-indent* regardless of the current trace level.
-
+
CCL:TRACE-FUNCTION
-
+
CCL:*TRACE-BAR-FREQUENCY* [Variable]
@@ -3215,5 +3215,5 @@
@@ -3254,5 +3254,5 @@
@@ -3433,5 +3433,5 @@
domain---This is used to indicate where the external
@@ -3467,5 +3467,5 @@
Despite the function's name, it doesn't necessarily create a
@@ -3635,5 +3635,5 @@
@@ -4197,5 +4197,5 @@
@@ -4240,5 +4240,5 @@
@@ -4286,5 +4286,5 @@
Clozure CL sets up logical pathname translations for logical hosts: The
-
+
CCL:MAP-FILE-TO-IVECTOR
-
+
CCL:UNMAP-IVECTOR
-
+
CCL:MAP-FILE-TO-OCTET-VECTOR
-
+
CCL:UNMAP-OCTET-VECTOR
Clozure CL provides the
function As of Clozure CL 1.2, the constant
-
+
SAVE-APPLICATION
If true, saves the image as a native (ELF, Mach-O, PE)
+ shared library. (On platforms where this isn't yet supported,
+ a warning is issued and the option is ignored.)
+
@@ -4904,5 +4916,5 @@
@@ -4951,5 +4963,5 @@
@@ -5009,5 +5021,5 @@
@@ -5183,5 +5195,5 @@
@@ -5217,5 +5229,5 @@
@@ -5303,5 +5315,5 @@
@@ -5603,5 +5615,5 @@
@@ -5625,5 +5637,5 @@
@@ -5651,5 +5663,5 @@
@@ -5677,5 +5689,5 @@
@@ -5708,5 +5720,5 @@
@@ -5735,5 +5747,5 @@
@@ -5758,5 +5770,5 @@
@@ -5785,5 +5797,5 @@
@@ -5812,5 +5824,5 @@
@@ -5979,5 +5991,5 @@
@@ -6004,5 +6016,5 @@
@@ -6040,5 +6052,5 @@
@@ -6075,5 +6087,5 @@
@@ -6106,5 +6118,5 @@
@@ -6336,5 +6348,5 @@
-
+
BUILD-APPLICATION &key
( process-suspend was previously called
@@ -7659,5 +7671,5 @@
@@ -7712,5 +7724,5 @@
It would be nice to have more discussion of what it means
@@ -7856,5 +7868,5 @@
It would probably be better for result
@@ -7995,10 +8007,10 @@
This should arguably be SETFable, but doesn't seem to
@@ -8287,5 +8299,5 @@
Advises the OS scheduler that the current thread has nothing
@@ -8296,10 +8308,10 @@
This is a holdover from the days of cooperative
@@ -8324,5 +8336,5 @@
Executes body
@@ -8505,5 +8517,5 @@
Creates and returns an object of type CCL::READ-WRITE-LOCK.
@@ -8711,10 +8723,10 @@
There probably should be some way to
@@ -8739,5 +8751,5 @@
result should probably be interpreted
@@ -8902,5 +8914,5 @@
result should probably be interpreted
@@ -8946,5 +8958,5 @@
fd---a file descriptor, which is a non-negative integer
@@ -8996,5 +9008,5 @@
@@ -9042,5 +9054,5 @@
fd---a file descriptor, which is a non-negative integer
@@ -9050,5 +9062,5 @@
@@ -9093,5 +9105,5 @@
process---a process, typically created by process-run-function or by make-process Waits for the specified process to terminate. If the
@@ -9360,5 +9372,5 @@
address-family---The address/protocol family of this socket. Currently
@@ -9460,5 +9472,5 @@
Creates and returns a new socket Extracts the first connection on the queue of pending
@@ -9513,5 +9525,5 @@
Converts a dotted-string representation of a host address to
@@ -9541,5 +9553,5 @@
ipaddr---A 32-bit integer representing an internet host address Converts a 32-bit unsigned IP address into octets. ipaddr---a 32-bit integer representing an internet host address Converts a 32-bit unsigned IP address into a host name
@@ -9596,5 +9608,5 @@
host---Specifies the host. It can be either a host name
@@ -9604,5 +9616,5 @@
Converts a host spec in any of the acceptable formats into a
@@ -9624,5 +9636,5 @@
port---Specifies the port. It can be either a string, such as
@@ -9633,5 +9645,5 @@
Finds the port number for the specified port and protocol Reads a UDP packet from a socket. If no packets are
@@ -9707,5 +9719,5 @@
Send a UDP packet over a socket. socket---The socket to shut down (typically a tcp-stream) Shuts down part of a bidirectional connection. This is
@@ -9769,10 +9781,10 @@
Returns the native OS's representation of the socket, or
@@ -9799,10 +9811,10 @@
Returns the 32-bit unsigned IP address of the remote host,
@@ -9824,10 +9836,10 @@
Returns the remote port number, or NIL if the socket is not
@@ -9849,10 +9861,10 @@
Returns 32-bit unsigned IP address of the local host. Returns the local port number Returns :internet or :file, as appropriate. Returns :active for tcp-stream, :passive for
@@ -9946,10 +9958,10 @@
Returns the socket format as specified by the :format
@@ -9971,10 +9983,10 @@
returns :stream for tcp-stream and listener-socket, and
@@ -9995,10 +10007,10 @@
simple-error The OS error code of the error A symbol representing the error code in a more
@@ -10072,10 +10084,10 @@
A string describing the context where the error happened. On
@@ -10098,5 +10110,5 @@
The close generic function can be applied to sockets. It
@@ -10130,5 +10142,5 @@
executes body with var bound to the result of applying
@@ -10269,5 +10281,5 @@
program---A string or pathname which denotes an executable file.
@@ -10320,5 +10332,5 @@
Runs the specified program in an external (Unix) process,
@@ -10340,5 +10352,5 @@
proc---An EXTERNAL-PROCESS, as returned by RUN-PROGRAM. Sends the specified "signal" to the specified
@@ -10369,10 +10381,10 @@
Returns the process id assigned to
@@ -10396,10 +10408,10 @@
Returns the stream created when the input argument to
@@ -10422,10 +10434,10 @@
Returns the stream created when the output argument to
@@ -10449,10 +10461,10 @@
Returns the stream created when the error argument to
@@ -10476,10 +10488,10 @@
Returns, as multiple values, a keyword denoting the status
@@ -10511,5 +10523,5 @@
A stream that is associated with a file descriptor has
attributes and accessors:
@@ -10800,5 +10812,5 @@
stream---a stream, presumably a fundamental-input-stream. Should try to read up to count elements from stream into the
@@ -11351,5 +11363,5 @@
stream---a stream, presumably a fundamental-output-stream. should try to write the first count elements of list to
@@ -11382,5 +11394,5 @@
stream---a stream, presumably a fundamental-input-stream should try to read successive elements from stream into
@@ -11421,5 +11433,5 @@
stream---a stream, presumably a fundamental-output-stream should try to write successive elements of vector to stream,
@@ -11459,5 +11471,5 @@
Returns the file descriptor associated with
@@ -11500,5 +11512,5 @@
stream---An input stream. The method defined on
@@ -11532,5 +11544,5 @@
Writes max-octets octets to stream from ivector, starting at
@@ -11538,5 +11550,5 @@
Use of oprofile and its companion programs isn't really documented here; what
- is described is a way of generating symbolic information that enables profiling
- summaries generated by the Use of oprofile and its companion programs isn't really documented
+ here; what is described is a way of generating symbolic information that
+ enables profiling summaries generated by the Modern Linux uses the 'ELF" (Executable and Linking Format) object file
- format; the oprofile tools can associate symbolic names with addresses in a
- memory-mapped file if that file appears to be an ELF object file and if it
- contains ELF symbol information that describes those memory regions. So, the
- general idea is to make a lisp heap image that looks enough like an ELF shared
- library to fool the Modern Linux uses the 'ELF" (Executable and Linking Format) object
+ file format; the oprofile tools can associate symbolic names with
+ addresses in a memory-mapped file if that file appears to be an ELF
+ object file and if it contains ELF symbol information that describes
+ those memory regions. So, the general idea is to make a lisp heap image
+ that looks enough like an ELF shared library to fool the
+ In order to create a lisp heap image which can be used for
- generate a file that contains ELF symbol information describing the
- names and addresses of all lisp functions. generate a file that contains ELF symbol information
+ describing the names and addresses of all lisp functions. This step involves doing (from within Clozure CL) The argument to CCL::WRITE-ELF-SYMBOLS-TO-FILE can be any writable
- pathname. The function will do whatever's necessary to nail lisp functions
- down in memory (so that they aren't moved by GC), then write an ELF object
- file to the indicated pathname. This typically takes a few seconds. The argument to CCL::WRITE-ELF-SYMBOLS-TO-FILE can be any
+ writable pathname. The function will do whatever's necessary to nail
+ lisp functions down in memory (so that they aren't moved by GC),
+ then write an ELF object file to the indicated pathname. This
+ typically takes a few seconds. Generate a lisp heap image in which the ELF symbols generated in the
- previous step are prepended. The function CCL:SAVE-APPLICATION provides a :PREPEND-KERNEL argument,
- which is ordinarily used to save a standalone application in which the kernel
- and heap image occupy a single file. :PREPEND-KERNEL doesn't really care what
- it's prepending to the image, and we can just as easily ask it to prepend the
- ELF symbol file generated in the previous step. Generate a lisp heap image in which the ELF symbols generated
+ in the previous step are prepended. The function CCL:SAVE-APPLICATION provides a :PREPEND-KERNEL
+ argument, which is ordinarily used to save a standalone application
+ in which the kernel and heap image occupy a single file.
+ :PREPEND-KERNEL doesn't really care what it's prepending to the
+ image, and we can just as easily ask it to prepend the ELF symbol
+ file generated in the previous step. any lisp code sampled by oprofile in that image will be identified
- "symbolically" by any lisp code sampled by oprofile in that image will be
+ identified "symbolically" by CCL::WRITE-ELF-SYMBOLS-TO-FILE currently only works on x86-64; it certainly
- -could- be made to work on ppc32/ppc64 as well. So far, no one has been able to make oprofile/opreport options that're
- supposed to generate call-stack info generate meaningful call-stack info. As of a few months ago, there was an attempt to provide symbol info for
- oprofile/opreport "on the fly", e.g., for use in JIT compilation or other
- incremental compilations scenarios. That's obviously more nearly The Right Thing,
- but it might be awhile before that experimental code makes it into widespread
- use. CCL::WRITE-ELF-SYMBOLS-TO-FILE currently only works on x86-64; it
+ certainly -could- be made to work on ppc32/ppc64 as well. So far, no one has been able to make oprofile/opreport options
+ that're supposed to generate call-stack info generate meaningful
+ call-stack info. As of a few months ago, there was an attempt to provide symbol
+ info for oprofile/opreport "on the fly", e.g., for use in JIT
+ compilation or other incremental compilation scenarios. That's obviously
+ more nearly The Right Thing, but it might be awhile before that
+ experimental code makes it into widespread use. Apple's CHUD package provides libraries, kernel extensions, and a
+ set of graphical and command-line programs that can be used to measure
+ many aspects of application and system performance. One of these programs is the Shark application (often installed in
+ "/Developer/Applications/Performance Tools/Shark.app"), which provides a
+ graphical user interface for exploring and analyzing profiling results and
+ provides tools for creating "sampling configurations" (see below), among
+ other things. Use of Shark isn't really documented here (a Shark manual is
+ available at "Developer/Documentation/CHUD/Shark/ SharkUserGuide.pdf");
+ what is described is a way of providing information about Lisp function
+ names and addresses so that Shark can meaningly identify those functions
+ in its output. Apple's CHUD metering tools are available (as of this writing) from:
- ftp://ftp.apple.com/developer/Tool_Chest/Testing_-_Debugging/Performance_tools/. The CHUD tools are also generally bundled with Apple's XCode tools. CHUD
- 4.5.0 (which seems to be bundled with XCode 3.0) seems to work well with this
- interface; later versions may have problems. Versions of CHUD as old as 4.1.1 may
- work with 32-bit PPC versions of CCL; later versions (not sure exactly -what-
- versions) added x86, ppc64, and x86-64 support. One way to tell whether any version of the CHUD tools is installed is to try
- to invoke the "shark" command-line program (/usr/bin/shark) from the shell: and verifying that that prints a usage summary. CHUD consists of several components, including command-line programs, GUI
- applications, kernel extensions, and "frameworks" (collections of libraries,
- headers, and other resources which applications can use to access functionality
- provided by the other components.) Past versions of Clozure CL/OpenMCL have used the
- CHUD framework libraries to control the CHUD profiler. Even though the rest of
- CHUD is currently 64-bit aware, the frameworks are unfortunately still only
- available as 32-bit libraries, so the traditional way of controlling the profiling
- facility from Clozure CL has only worked from DarwinPPC32 versions. Two of the CHUD component programs are of particular interest: The "Shark" application (often installed in
- "/Developer/Applications/Performance Tools/Shark.app"), which provides a
- graphical user interface for exploring and analyzing profiling results and
- provides tools for creating "sampling configurations" (see below), among other
- things. The "shark" program ("/usr/bin/shark"), which can be used to control the
- CHUD profiling facility and to collect sampling data, which can then be
- displayed and analyzed in Shark.app. The fact that these two (substantially different) programs have names that
- differ only in alphabetic case may be confusing. The discussion below tries to
- consistently distinguish between "the shark program" and "the Shark
- application". Apple's CHUD tools have been distributed with the last several
+ XCode releases. One way to determine whether or not the tools are
+ installed is to run: in a terminal or Emacs shell buffer. If that returns output
+ like then the CHUD package is installed. Output like strongly suggests that it isn't ... Shark can only properly identify functions that're defined in a
+ shared library that's loaded by the target application. (Any other
+ functions will be identified by a hex address described as being in an
+ "Unknown Library"; the hex address is generally somewhat near the actual
+ function, but it's determined heuristically and isn't always
+ accurate.) For those reasons, it's desirable to load the code that you wish
+ to profile in one lisp session, save a native (Mach-O library) image,
+ and invoke Shark in a new session which uses that native image. (It may
+ also be useful to load the CHUD-METERING module, which defines
+ CHUD:METER and friends. and, a few seconds after the result is returned, a file whose name is of
- the form "session_nnn.mshark" will open in Shark.app. The fist time that CHUD:METER is used in a lisp session, it'll do a few
- things to prepare subsequent profiling sessions. Those things include: and, a few seconds after the result is returned, a file whose name
+ is of the form "session_nnn.mshark" will open in Shark.app. The fist time that CHUD:METER is used in a lisp session, it'll do
+ a few things to prepare subsequent profiling sessions. Those things
+ include: creating a directory to store files that are related to using the CHUD
- tools in this lisp session. This directory is created in the user's home
- directory and has a name of the form: creating a directory to store files that are related to using
+ the CHUD tools in this lisp session. This directory is created in
+ the user's home directory and has a name of the form: where <pid> is the lisp's process id, <lisp-kernel> is the
- name of the lisp kernel (of all things ...), and the other values provide a
- timestamp. does whatever needs to be done to ensure that currently-defined lisp
- functions don't move around as the result of GC activity, then writes a text
- file describing the names and addresses of those functions to the
- profiling-session directory created above. (The naming conventions for and
- format of that file are described in run the shark program ("/usr/bin/shark") and wait until it's ready to
- receive signals that control its operation. run the shark program ("/usr/bin/shark") and wait until it's
+ ready to receive signals that control its operation. This startup activity typically takes a few seconds; after it's been
- completed, subsequent use of CHUD:METER doesn't involve that overhead. (See the
- discussion of :RESET below.) After any startup activity is complete, CHUD:METER arranges to send a
- "start profiling" signal to the running shark program, executes the form, sends
- a "stop profiling" signal to the shark program, and reads its diagnostic output,
- looking for the name of the ".mshark" file it produces. If it's able to find
- this filename, it arranges for "Shark.app" to open it. This startup activity typically takes a few seconds; after it's
+ been completed, subsequent use of CHUD:METER doesn't involve that
+ overhead. (See the discussion of :RESET below.) After any startup activity is complete, CHUD:METER arranges to
+ send a "start profiling" signal to the running shark program, executes
+ the form, sends a "stop profiling" signal to the shark program, and
+ reads its diagnostic output, looking for the name of the ".mshark" file
+ it produces. If it's able to find this filename, it arranges for
+ "Shark.app" to open it. use "time based" sampling, to periodically interrupt the lisp
- process and note the value of the program counter and at least a few levels of
- call history. This is known as "the default configuration"; it's possible to use items
- on the "Config" menu in the Shark application to create alternate configurations
- which provide different kinds of profiling parameters and to save these
- configurations in files for subsequent reuse. (The set of things that CHUD
- knows how to monitor is large and interesting.) You use alternate profiling configurations (created and "exported" via
- Shark.app) with CHUD:METER, but the interface is a little awkward. This is known as "the default configuration"; it's possible to use
+ items on the "Config" menu in the Shark application to create alternate
+ configurations which provide different kinds of profiling parameters and
+ to save these configurations in files for subsequent reuse. (The set of
+ things that CHUD knows how to monitor is large and interesting.) You use alternate profiling configurations (created and "exported"
+ via Shark.app) with CHUD:METER, but the interface is a little
+ awkward.
-
- CHUD:*SHARK-CONFIG-FILE* [Variable]
- When non-null, this should be the pathname of an alternate profiling
- configuration file created by the "Config Editor" in Shark.app.
-
- CHUD:METER form &key (reset nil) (debug-output nil) [Macro]
- Executes FORM (an arbitrary lisp form) and returns whatever result(s) it
- returns, with CHUD profiling enabled during the form's execution. Tries to
- determine the name of the session file (*.mshark) to which the shark program
- wrote profiling data and opens this file in the Shark application.
+ CHUD:*SHARK-CONFIG-FILE*
+ [Variable] When non-null, this should be the pathname of an alternate
+ profiling configuration file created by the "Config Editor" in
+ Shark.app. CHUD:METER form &key (reset nil)
+ (debug-output nil) [Macro] Executes FORM (an arbitrary lisp form) and returns whatever
+ result(s) it returns, with CHUD profiling enabled during the form's
+ execution. Tries to determine the name of the session file (*.mshark) to
+ which the shark program wrote profiling data and opens this file in the
+ Shark application. Arguments: when non-nil, causes output generated by the shark program to be
- echoed to *TERMINAL-IO*. For debugging. when non-nil, causes output generated by the shark program
+ to be echoed to *TERMINAL-IO*. For debugging. when non-nil, terminates any running instance of the shark program
- created by previous invocations of CHUD:METER in this lisp session,
- generates a new .spatch file (describing the names and addresses of lisp
- functions), and starts a new instance of the shark program; if
- CHUD:*SHARK-CONFIG-FILE* is non-NIL when this new instance is started,
- that instance is told to use the specified config file for profiling (in
- lieu of the default profiling configuration.) when non-nil, terminates any running instance of the shark
+ program created by previous invocations of CHUD:METER in this lisp
+ session, generates a new .spatch file (describing the names and
+ addresses of lisp functions), and starts a new instance of the
+ shark program; if CHUD:*SHARK-CONFIG-FILE* is non-NIL when this
+ new instance is started, that instance is told to use the
+ specified config file for profiling (in lieu of the default
+ profiling configuration.) Both Dan Knapp and Hamilton Link have posted similar CHUD interfaces to
- openmcl-devel in the past; Hamilton's also reported bugs in the spatch mechanism
- to CHUD developers (and gotten those bugs fixed.) Both Dan Knapp and Hamilton Link have posted similar CHUD
+ interfaces to openmcl-devel in the past; Hamilton's also reported bugs
+ in the spatch mechanism to CHUD developers (and gotten those bugs
+ fixed.) Reads a symbol from the current input stream, with *PACKAGE*
@@ -15903,5 +15931,5 @@
In In In In If completely is T, sets the
@@ -16177,5 +16205,5 @@
Proclaims name
@@ -16230,5 +16258,5 @@
If name is non-NIL, defines name to be an alias for the
@@ -16272,5 +16300,5 @@
If there is already an EXTERNAL-ENTRY-POINT for
@@ -16313,5 +16341,5 @@
Calls the foreign function at the address obtained by
@@ -16353,5 +16381,5 @@
Calls the foreign function at address entrypoint passing the
@@ -16390,5 +16418,5 @@
Calls the foreign function at address entrypoint passing the
@@ -16428,10 +16456,10 @@
Tries to resolve the address of the foreign symbol
@@ -16456,10 +16484,10 @@
compile-file. fasl files store the
@@ -1756,5 +1756,5 @@
see
Table 3.1, âPlatform-specific filename conventionsâ ccl/lisp-kernel/; each such
-
+
contains a Makefile and may contain some auxiliary files (linker
scripts, etc.) that are used to build the lisp kernel on a
@@ -2608,5 +2608,5 @@
keyword
global-value}* {spec |
@@ -3052,15 +3052,15 @@
spec &key {keyword value}* [Function]
ccl and homeCCL logical host should point to the
ccl directory. It is used for a variety of
@@ -4440,5 +4440,5 @@
platforms.pathname
@@ -4500,5 +4500,5 @@
a memory error.displaced-array
@@ -4512,5 +4512,5 @@
target is an empty vector (of length zero).pathname
@@ -4522,5 +4522,5 @@
bytes.displaced-array
@@ -4561,5 +4561,5 @@
static.CCL:SAVE-APPLICATION, which creates a file
@@ -4695,5 +4695,5 @@
converted, because address 0 can always be relied upon to refer to
the same thing.CCL:+NULL-PTR+
refers to a MACPTR object that points to address 0.opencml
- or opencml64 script.
+ command-line parameter to the ccl
+ or ccl64 script.
filename
@@ -4719,4 +4719,5 @@
(mode #o644)
prepend-kernel
+ native
[Function]
name "MyApplication")
@@ -6768,5 +6780,5 @@
@@ -12339,20 +12351,25 @@
oprofile is
- a system-level profiler that's available for most modern Linux distributions.opreport program to identify lisp functions
- meaningfully.oprofile is a
+ system-level profiler that's available for most modern Linux
+ distributions.opreport program
+ to identify lisp functions meaningfully.oprofile tools (we don't actually load heap
- images via ELF dynamic linking technology, but we can make it look like we
- did.)oprofile tools (we don't actually load heap images via ELF
+ dynamic linking technology, but we can make it look like we did.)
@@ -12423,5 +12451,5 @@
oprofile itself, which is almost certainly available via
- your distribution's package management system if not already
- preinstalled.oprofile itself, which is almost certainly
+ available via your distribution's package management system if not
+ already preinstalled.libelf, which provides utilities for reading and writing
- ELF files (and is likewise likely preinstalled or readily installable.)libelf, which provides utilities for reading and
+ writing ELF files (and is likewise likely preinstalled or readily
+ installable.) Somewhat confusingly, there are two libelf
+ implementations in widespread use on Linux, and different
+ distributions refer to them by different names (they may be
+ available as part of an 'elfutils' package.) The oprofile insterface
+ was designed to work with a libelf implementation whose version
+ number is currently around 147; the other (incompatible) libelf
+ implementation has a version number around 0.8. It may be necessary
+ to install the corresponding development package (-dev or -devel,
+ usuallly) in order to actually be able to use the libelf shared
+ library.oprofile- based profiling, we need to:oprofile- based profiling, we need to:
@@ -12430,6 +12458,6 @@
@@ -12517,5 +12547,5 @@
;;; we simply flush profiling data to disk, where 'opreport' can
;;; find it.
-
+
[~] gb@rinpoche> sudo opcontrol --dump
@@ -12544,13 +12574,14 @@
@@ -12440,17 +12468,19 @@
? (ccl::write-elf-symbols-to-file "home:elf-symbols")
-
? (save-application "somewhere/image-for-profiling"
@@ -12461,6 +12491,6 @@
shell> ccl64 somewhare/image-for-profiling
- opreport.opreport.
-shell> shark --help
-
-
-
- $ /usr/bin/shark -v
+ shark 4.7.3 (365)
+ shark: Command not found.
+
-? (defun fact (n) (if (zerop n) 1 (* n (fact (1- n)))))
+
[src/ccl-dev] gb@antinomial> ccl64
+Welcome to Clozure Common Lisp Version 1.7-dev-r14624M-trunk (DarwinX8664)!
+? (defun fact(n) (if (zerop n) 1 (* n (fact (1- n)))))
FACT
? (require "CHUD-METERING")
"CHUD-METERING"
("CHUD-METERING")
-? (chud:meter (null (fact 10000)))
-NIL ; since that large number is not NULL
-
-
profiling-session-<lisp-kernel>-<pid>_<mm>-<dd>-<yyyy>_<h>.<m>.<s>
- CCL 1.2 and later, the #& reader macro can be used to
@@ -15962,5 +15990,5 @@
CCL 0.14.2 and later, the #? reader macro can be used
@@ -16009,5 +16037,5 @@
CCL 1.2 and later, the #/ reader macro can be used to
@@ -16112,5 +16140,5 @@
CCL 1.2 and later, the #> reader macro reads
@@ -16141,5 +16169,5 @@