Known issues

Tracing multiple applications

The Viewer can receive traces from different applications at the same time. However, the resulting sequence diagram may not be correct.

The next major Lumos version will come with improved support for this use case.

Tracing continuity

If the tracing is stopped and resumed during a debugging session, this may cause issues in the sequence diagram drawing. The viewer might potentially miss module start/stop events and lose consistency in its internal memory.

We recommend not stopping the tracing while your debugging is not finished.
If you want to view a specific part of your application’s communication, you can use the filter functions to narrow down the displayed elements in the sequence diagram.

Tracing DQMH module

To get an accurate sequence diagram, you must start and stop your modules with the public API.

Starting execution of the module running the will result in incorrect or less accurate sequence diagram.