Dynamic verification backends via reflection, stack trace messaging, proper logging support

[viper-admin]

Pull request :twisted_rightwards_arrows: created by @aterga on 2018-03-31 13:49 Last updated on 2018-05-10 21:09 Original Bitbucket pull request id: 5

Participants:

• @aterga
• @vakaras (reviewer)

Source: https://github.com/viperproject/viperserver/commit/6dde36054b40718cdbec2be9bb73e489d33c170a on branch arshavir/viperserver-dynamic-backends/default Destination: https://github.com/viperproject/viperserver/commit/f2979f69cd15eb879675516eaa4e3aa04d4e590f on branch master Marge commit: https://github.com/viperproject/viperserver/commit/6dde36054b40718cdbec2be9bb73e489d33c170a

State: MERGED

• Increased the maximum number of messages in the reporter's message buffer (from 100 to 1000).

• Added support for dynamically loading verification beckends (SilFrontend implementations).

• Update the logger dependencies (entirely switch to pure logback since customization beyond scala-logging is needed anyway).

• Implemented JSON marshaller for reporter.ExceptionReport

• Impelmented proper logging; exceptions in verification backends are sent to the IDE via reporter.ExceptionReport.

• Support SilFrontend implementations with the second constructor argument (i.e., reporter) in dynamic verification backend support.

• Implement getLogFileWithGuarantee(): log file will be created in case a writable directory is passed via --logFile.

• Changed the order of prints in ViperServerRunner.main (for IDE compatibility).

[viper-admin]

@aterga commented on 2018-03-31 13:50

Depends on https://github.com/viperproject/silver/pull/395