04-20-2010 02:50 PM
I'm new to BB development and am using the Eclipse plugin for coding/debugging. The Eclipse console window seems to show an endless stream of messages from the system. Things like:
JPGENC 7 ms
JPGENC 0 ms
JPGENC 70 ms
JPGENC 0 ms
JPGENC 0 ms
JPGENC 70 ms
JPGENC 0 ms
JPGENC 7 ms
JPGENC 54 ms
JPGENC 7 ms
JPGENC 0 ms
JVM: bklt @85945: timer
JVM: bklt[1] @85945: idle 15
JVM: bklt[1] @85945: enableBacklight 0
JVM: bklt[1]: setTimeout 30
VM:IGCSc=0
VM:+GC(f)w=9
VM:-GCt=19,b=1,r=0,g=f,w=9
VM:QUOT t=2
VM:+CR
VM:-CR=3
VM
ISVt=0,h=1616,id=d15a33128dfbb5d9
Does anyone really want to see this? I really interferes with seeing my own logging information. Is there a way to turn off (or filter) the system logging output?
Solved! Go to Solution.
04-20-2010 03:51 PM
You have no control over this.
As a work-around, we prefix out console logging with a specific application value, like FOO:
Then we can copy the console output and filter using fgrep looking for "FOO:" in the first positions of each line.
04-20-2010 04:04 PM - edited 04-20-2010 04:06 PM
I actually brought this up before. It's been confirmed that no such option exists, but I've put in a feature request using the Bug Tracker, so it may be included in future releases of the simulators/JDEs.
Hope that helps,
~Dom
EDIT: https://www.blackberry.com/jira/browse/TOOL-136
09-20-2010 10:04 AM
I got fed up with this issue so I eventually developed an eclipse plugin enabling me to filter out text (in runtime) based on some prefix I add to my debug prints.
You can download the plugin from here: http://code.google.com/a/eclipselabs.org/p/console
04-06-2011 11:01 AM
yes this is insane , i doubt there is no flag to shut down the jvm and keep system.out/err
07-19-2011 12:11 PM
Yoav,
I am about what is robably an incredibly stupid question. Brace yourself. :-)
First, some background. I'm using:
Eclipse SDK
Version: 3.6.2
Build id: M20110210-1200
I've installed CG per instructions. i've input
'INIT'
in CG regex (which is accepted by a regex tester) but I get no matches from my source console which has
multiple occurrences of INIT_NEAR (but not at the head of the line).
Duh?
07-19-2011 02:11 PM