Debugging RedDeer
From time to time you can observed unexpected behavior that is not caused by your code but by a bug in RedDeer itself. This chapter covers some basic approaches of howto find a problem and gather enough information for issue reporting or fixing a problem
There is a standard RedDeer log produced on in your primary output (either terminal or Eclipse console view).
INFO [thread][class] Log message-1
INFO [thread][class] Log message-n
...
ERROR [thread][class] Something bad and unexpected happened
TRACE [thread][class] Some additional information for the
INFO [thread][class] Log message-n+1
When you want more detail information about what is happening you should enable DEBUG messages. You can do it by setting appropriate vm variable log.debug to true either in eclipse
-Dlog.debug=true
Then after test restart you'll also see messages marked by DEBUG
DEBUG [thread][class] Debug message
...
Of course you can also use Eclipse debugger and set your breakpoints to track cause of the problem right in the source code. But this is not specific so you can follow some good tutorial on the web for example this one