X-Git-Url: http://info.iut-bm.univ-fcomte.fr/pub/gitweb/simgrid.git/blobdiff_plain/8452130aa48a4ecfce975c1fcf002c3b20fb6480..eb5b6b0c3c4d9a38bb205b2c8bc9aeeba8674a25:/src/xbt/log.c diff --git a/src/xbt/log.c b/src/xbt/log.c index b5bab4af52..374191a92c 100644 --- a/src/xbt/log.c +++ b/src/xbt/log.c @@ -420,6 +420,16 @@ The following example resets the additivity of the xbt category to true (which i option and specify the max file size. This would be a nice default for non-kernel applications. - Careful, category names are global variables. + - When writing a log format, you often want to use spaces. If you don't + protect these spaces, they are used as configuration elements separators. + For example, if you want to remove the date from the logs, you want to pass the following + argument on the command line. The outer quotes are here to protect the string from the shell + interpretation while the inner ones are there to prevent simgrid from splitting the string + in several log parameters (that would be invalid). + \verbatim --log="'root.fmt:%l: [%p/%c]: %m%n'"\endverbatim + Another option is to use the SimGrid-specific format directive \%e for + spaces, like in the following. + \verbatim --log="root.fmt:%l:%e[%p/%c]:%e%m%n"\endverbatim \section log_internals 4. Internal considerations @@ -1062,7 +1072,7 @@ void xbt_log_threshold_set(xbt_log_category_t cat, static xbt_log_setting_t _xbt_log_parse_setting(const char *control_string) { - + const char *orig_control_string = control_string; xbt_log_setting_t set = xbt_new(s_xbt_log_setting_t, 1); const char *name, *dot, *eq; @@ -1085,7 +1095,7 @@ static xbt_log_setting_t _xbt_log_parse_setting(const char *control_string) control_string += strcspn(control_string, " "); xbt_assert(*dot == '.' && (*eq == '=' || *eq == ':'), - "Invalid control string '%s'", control_string); + "Invalid control string '%s'", orig_control_string); if (!strncmp(dot + 1, "threshold", (size_t) (eq - dot - 1))) { int i;