[Bro-Dev] [JIRA] (BIT-646) Cleanup interpreter error handling.

Jon Siwek (JIRA) jira at bro-tracker.atlassian.net
Tue Mar 17 09:22:00 PDT 2015

     [ https://bro-tracker.atlassian.net/browse/BIT-646?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jon Siwek updated BIT-646:
    Resolution: Fixed
        Status: Closed  (was: Open)

Not sure how useful keeping this open is, so closing, but feel free to re-open if anyone feels it needs a more thorough audit.

> Cleanup interpreter error handling.
> -----------------------------------
>                 Key: BIT-646
>                 URL: https://bro-tracker.atlassian.net/browse/BIT-646
>             Project: Bro Issue Tracker
>          Issue Type: Task
>          Components: Bro
>            Reporter: Robin Sommer
>              Labels: language
>             Fix For: 2.4
> From 15ab2874369b5d7a3e6a14df24b141fa759999bb (which has been merged into master):
> {noformat}
>  Currently, a lot of interpreter runtime errors, such as an access to
>     an unset optional record field, cause Bro to abort with an internal
>     error. This is an experimental branch that turns such errors into
>     non-fatal runtime errors by internally raising exceptions. These are
>     caught upstream and processing continues afterwards.
>     For now, not many errors actually raise exceptions (the example above
>     does though). We'll need to go through them eventually and adapt the
>     current Internal() calls (and potentially others). More generally, at
>     some point we should cleanup the interpreter error handling (unifying
>     errors reported at parse- and runtime; and switching to exceptions for
>     all Expr/Stmt/Vals). But that's a larger change and left for later.
> {noformat}

This message was sent by Atlassian JIRA

More information about the bro-dev mailing list