02-19-2012 10:06 AM - edited 02-19-2012 10:07 AM
Is it possible to somehow debug the AIR native extensions when running on the PlayBook, or at least get some output/print-debugging feedback?
I tried it like described in this tutorial but don't know where the fprintf/fflush output can be found ![]()
Solved! Go to Solution.
02-19-2012 10:29 AM
The stdout and stderr are always redirected to the logs/log file under the current directory of your app. You can look at that directly, assuming you don't already have some other means, by using SSH to connect to your PlayBook or simulator and find the appdata folder for your app.
Some background on the filesystem layout is http://supportforums.blackberry.com/t5/Tablet-OS-S
Numerous other threads and blog posts have covered connecting via SSH.
02-19-2012 10:37 AM
02-19-2012 10:57 AM - edited 02-19-2012 10:59 AM
You can also attach Momentics to the running AIR debug launcher (adl) process on your Playbook and set breakpoints in your ANE, step through code, inspect variables etc using the Momentics debugger in parallel with the Flash Builder debugger.
02-19-2012 11:03 AM
peter9477 wrote:
The stdout and stderr are always redirected to the logs/log file under the current directory of your app. You can look at that directly, assuming you don't already have some other means, by using SSH to connect to your PlayBook or simulator and find the appdata folder for your app. [...] Numerous other threads and blog posts have covered connecting via SSH.
Momentics contains a few very handy views for this: a target file system explorer and an SSH termnal which handles token exchange for you. Look under Window > Views. Much easier than messing around with an SSH client...
02-19-2012 12:02 PM