t is documented, it's just not obvious.
It's mentioned in the release notes as the first item under Known Limitations.
The qDebug() function
- In this release, the qDebug() function does not work the same way as it did in previous releases. Previously, when you used this function in your JavaScript/QML code, the function sent the debug information to the console, and you could view the information in the Console view in the IDE. Now, this function does not send output to the console. Instead, this function sends debug information to the slogger2 log.
To see debug information that is output from qDebug(), you need to access the slogger2 logs as follows:
1. In the IDE, in the Target Navigator view, right-click the device target. Click Launch SSH Session.
2. In the terminal that appears, do one of the following:
a. To view the current slogger2 logs, type slog2info.
b. To view real-time output for the processes that are being debugged (for applications that are running in development mode), type slog2info -w.
c. To view help information on slogger2, type slog2info -h.
You can also access the log files directly in the /tmp/slogger22 on the device and run these logs through slog2info at a later time.
