Overhauling the internal reporting of messages to the user.

The Logger class is now in charge of reporting all errors, warnings,
informational messages, weirds, and syslogs. All other components
route their messages through the global bro_logger singleton.

The Logger class comes with these reporting methods:

    void Message(const char* fmt, ...);
    void Warning(const char* fmt, ...);
    void Error(const char* fmt, ...);
    void FatalError(const char* fmt, ...); // Terminate Bro.
    void Weird(const char* name);
    [ .. some more Weird() variants ... ]
    void Syslog(const char* fmt, ...);
    void InternalWarning(const char* fmt, ...);
    void InternalError(const char* fmt, ...); // Terminates Bro.

See Logger.h for more information on these.

Generally, the reporting now works as follows:

    - All non-fatal message are reported in one of two ways:

        (1) At startup (i.e., before we start processing packets),
            they are logged to stderr.

        (2) During processing, they turn into events:

            event log_message%(msg: string, location: string%);
            event log_warning%(msg: string, location: string%);
            event log_error%(msg: string, location: string%);

            The script level can then handle them as desired.

            If we don't have an event handler, we fall back to
            reporting on stderr.

    - All fatal errors are logged to stderr and Bro terminates
      immediately.

    - Syslog(msg) directly syslogs, but doesn't do anything else.

The three main types of messages can also be generated on the
scripting layer via new Log::* bifs:

    Log::error(msg: string);
    Log::warning(msg: string);
    Log::message(msg: string);

These pass through the bro_logger as well and thus are handled in the
same way. Their output includes location information.

More changes:

    - Removed the alarm statement and the alarm_hook event.

    - Adapted lots of locations to use the bro_logger, including some
      of the messages that were previously either just written to
      stdout, or even funneled through the alarm mechanism.

    - No distinction anymore between Error() and RunTime(). There's
      now only one class of errors; the line was quite blurred already
      anyway.

    - util.h: all the error()/warn()/message()/run_time()/pinpoint()
      functions are gone. Use the bro_logger instead now.

    - Script errors are formatted a bit differently due to the
      changes. What I've seen so far looks ok to me, but let me know
      if there's something odd.

Notes:

    - The default handlers for the new log_* events are just dummy
      implementations for now since we need to integrate all this into
      the new scripts anyway.

    - I'm not too happy with the names of the Logger class and its
      instance bro_logger. We now have a LogMgr as well, which makes
      this all a bit confusing. But I didn't have a good idea for
      better names so I stuck with them for now.

      Perhaps we should merge Logger and LogMgr?
This commit is contained in:
Robin Sommer 2011-06-24 21:33:05 -07:00
parent ff7b92ffc8
commit 93894eed9b
140 changed files with 2453 additions and 1054 deletions

View file

@ -5,7 +5,7 @@
%expect 85
%token TOK_ADD TOK_ADD_TO TOK_ADDR TOK_ALARM TOK_ANY
%token TOK_ADD TOK_ADD_TO TOK_ADDR TOK_ANY
%token TOK_ATENDIF TOK_ATELSE TOK_ATIF TOK_ATIFDEF TOK_ATIFNDEF
%token TOK_BOOL TOK_BREAK TOK_CASE TOK_CONST
%token TOK_CONSTANT TOK_COPY TOK_COUNT TOK_COUNTER TOK_DEFAULT TOK_DELETE
@ -78,6 +78,7 @@
#include "DNS.h"
#include "RE.h"
#include "Scope.h"
#include "Logger.h"
#include "BroDoc.h"
#include "BroDocObj.h"
@ -562,7 +563,7 @@ expr:
int intval = t->Lookup(id->ModuleName(),
id->Name());
if ( intval < 0 )
internal_error("enum value not found for %s", id->Name());
bro_logger->InternalError("enum value not found for %s", id->Name());
$$ = new ConstExpr(new EnumVal(intval, t));
}
else
@ -689,7 +690,7 @@ enum_body_elem:
assert(cur_enum_type);
if ( $4->Type()->Tag() != TYPE_COUNT )
error("enumerator is not a count constant");
bro_logger->Error("enumerator is not a count constant");
else
cur_enum_type->AddName(current_module, $2, $4->InternalUnsigned(), is_export);
@ -707,7 +708,7 @@ enum_body_elem:
error message if users triy to use a negative integer (will also
catch other cases, but that's fine.)
*/
error("enumerator is not a count constant");
bro_logger->Error("enumerator is not a count constant");
}
| opt_doc_list TOK_ID
@ -827,7 +828,7 @@ type:
| TOK_UNION '{' type_list '}'
{
set_location(@1, @4);
error("union type not implemented");
bro_logger->Error("union type not implemented");
$$ = 0;
}
@ -843,7 +844,7 @@ type:
{
set_location(@1);
// $$ = new TypeList();
error("list type not implemented");
bro_logger->Error("list type not implemented");
$$ = 0;
}
@ -851,7 +852,7 @@ type:
{
set_location(@1);
// $$ = new TypeList($3);
error("list type not implemented");
bro_logger->Error("list type not implemented");
$$ = 0;
}
@ -1328,12 +1329,6 @@ stmt:
$$ = $2;
}
| TOK_ALARM expr_list ';'
{
set_location(@1, @3);
$$ = new AlarmStmt($2);
}
| TOK_PRINT expr_list ';'
{
set_location(@1, @3);
@ -1601,7 +1596,7 @@ resolve_id:
$$ = lookup_ID($1, current_module.c_str());
if ( ! $$ )
error("identifier not defined:", $1);
bro_logger->Error("identifier not defined:", $1);
delete [] $1;
}
@ -1658,7 +1653,7 @@ int yyerror(const char msg[])
strcat(msgbuf, "\nDocumentation mode is enabled: "
"remember to check syntax of ## style comments\n");
error(msgbuf);
bro_logger->Error(msgbuf);
return 0;
}