It is possible to fine-tune the behavior of the debugged runtime system
in various ways, both at compile time (setting C pre-processor symbols
and passing system properties to
SP_initialize()) and at runtime
(passing system properties as environment variables).
The system properties and environment variables that affect the debugged runtime system are,
yes, the runtime system will try to start a development system, as described above.
yes, has the same effect as
SP_USE_DEVSYS=yesand in addition tries to attach to the SICStus Prolog IDE (SPIDER). You have to tell SPIDER to ‘Attach to Prolog Process’, i.e. listen for an incoming connection. This command is available from the SICStus top-level view menu in SPIDER.
yes, will prevent the runtime system from calling
trace/0at initialization. This is useful if you prefer to manually enable the debugger later from your C or Prolog code.
no, will prevent the runtime system from starting as a development system. This may be useful in order to prevent inheriting
SP_ATTACH_SPIDERfrom the environment. The same effect can be obtained by passing the option --no-allow-devsys to spld when building the runtime system.
If your C code calls
SP_initialize() you can pass these system
properties in the call to
(see SP_initialize). You can also pass
these options to
SP_initialize() by setting the
macro. See the definition of
SP_initialize() in the header file
sictus/sicstus.h for details.