Welcome to the Official BlackBerry Support Community Forums. This is your resource to discuss support topics with your peers, and learn from each other. New to the forum? Please visit the ‘Getting Started’ link below.
Please use the Board search feature at upper right. Looking for "console debug" or various similar searches will get you many threads with answers and options.
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.
It shows all logs, even console.log() entries from Javascript.
they probably did it because writing to standard out is expensive vs whatever they mapped it to with slogger2, so for system performance they made it so all apps did this instead of worrying about developers leaving a lot of qDebug() code in the production codebases.
