2002-08-19 18:43:10 +00:00
|
|
|
<title>Core Client: Debugging</title>
|
2002-08-20 23:54:17 +00:00
|
|
|
<body bgcolor=ffffff>
|
|
|
|
<h2>Core Client: Debugging</h2>
|
|
|
|
<h3>Core client logging and error output</h3>
|
2002-04-30 22:22:54 +00:00
|
|
|
<p>
|
2002-08-19 18:43:10 +00:00
|
|
|
The core client writes error messages to stderr.
|
|
|
|
This mechanism is reserved for serious problems,
|
|
|
|
i.e. those that reflect bugs in the core
|
2002-07-29 19:01:38 +00:00
|
|
|
client program or conditions that require user intervention.
|
|
|
|
Specifically, The client verifies that arguments to functions have valid
|
2002-08-19 18:43:10 +00:00
|
|
|
values, and will print a message to stderr on an invalid argument.
|
|
|
|
These error messages are formatted as <tt>error: CLASS_NAME.function:
|
|
|
|
error_statement argument</tt>.
|
|
|
|
Common errors of this type include
|
|
|
|
unexpected NULL pointer arguments and negative lengths.
|
|
|
|
Error numbers
|
2002-07-29 19:01:38 +00:00
|
|
|
are defined in <b>lib/error_numbers.h</b>.
|
2002-04-30 22:22:54 +00:00
|
|
|
<p>
|
2002-08-19 18:43:10 +00:00
|
|
|
In addition, the core client can write a variety of "logging"
|
|
|
|
information to stdout.
|
|
|
|
The logging options are read from a file
|
|
|
|
<b>log_flags.xml</b>.
|
|
|
|
This file has the following format:
|
2002-04-30 22:22:54 +00:00
|
|
|
<pre>
|
2002-07-29 19:01:38 +00:00
|
|
|
<log_flags>
|
2002-04-30 22:22:54 +00:00
|
|
|
[ flags ]
|
2002-07-29 19:01:38 +00:00
|
|
|
</log_flags>
|
2002-08-19 18:43:10 +00:00
|
|
|
</pre>
|
|
|
|
The flags are as follows:
|
2002-04-30 22:22:54 +00:00
|
|
|
<dl>
|
2002-08-19 18:43:10 +00:00
|
|
|
<dt> <task/>
|
|
|
|
<dd> Log the start, restart and completion of computational tasks.
|
|
|
|
<dt> <file_xfer/>
|
|
|
|
<dd> Log the start, restart and completion of file transfers.
|
|
|
|
<dt> <sched_ops/>
|
|
|
|
<dd> Log connections with scheduling servers.
|
|
|
|
<dt> <state_debug/>
|
|
|
|
<dd> Log changes to the "client state" data structures.
|
|
|
|
<dt> <task_debug/>
|
|
|
|
<dd> Log debugging information about task execution.
|
|
|
|
<dt> <file_xfer_debug/>
|
|
|
|
<dd> Log debugging information about file transfers.
|
|
|
|
<dt> <sched_op_debug/>
|
|
|
|
<dd> Log the request and reply messages of exchanges with scheduling
|
2002-07-29 19:01:38 +00:00
|
|
|
servers.
|
2002-08-19 18:43:10 +00:00
|
|
|
<dt> <http_debug/>
|
|
|
|
<dd> Log debugging information about HTTP operations.
|
|
|
|
<dt> <time_debug/>
|
|
|
|
<dd> Log the passage of time.
|
|
|
|
<dt> <net_xfer_debug/>
|
|
|
|
<dd> Log debugging information about network communication.
|
2002-04-30 22:22:54 +00:00
|
|
|
</dl>
|
2002-07-29 19:01:38 +00:00
|
|
|
<h3>Application error output</h3>
|
2002-04-30 22:22:54 +00:00
|
|
|
<p>
|
2002-08-19 18:43:10 +00:00
|
|
|
The stderr of applications is automatically directed to a file. The
|
2002-07-29 19:01:38 +00:00
|
|
|
contents of this file are returned to the scheduling server and stored
|
|
|
|
in the database.
|