When a Blackberry phone is connected via USB and in debug mode, calls made to System.out.println() are visible in the log.
But is there any way to get access to "stdout" even from a program not in debug mode? Attaching with some command line program perhaps?
I worked around the issue by creating an over-the-network logging function.
If you have the JDE installed and BB plugged in via a USB:
JavaLoader.exe -usb eventLog > theLog.txt
This is often much more convenient for accessing the logs during dev.
There's no way to programmatically get the content though.
Related
I worked on a Console Application with a friend today. Is it possible to share the default console during a Live Share session? What I mean is that we had to compile and run our program manually through the default Windows Terminal to see output(which wasn't the best idea, there was a ton of empty lines displayed every time we would input anything), and debugging was impossible because we just couldn't see the console (only the host could).
According to the docs, it's possible to share the terminal in both VS Code and Visual Studio, but I don't think there's a way to share the console that comes up when you debug a console app. The solution I see is simply sharing a terminal, running your app in it manually and if you want debugging, you can try attaching the VS debugger to the console app's process after you start it manually by following this guide.
Currently I'm trying to debug an application, however, every time it crashes, I see this:
Instead of this:
As you can see, there's no Debug button, so I cannot debug the crash!
It only happens with this application; the button appears with every other app that crashes.
It looks like WER (Windows Error Reporting) is handling the crash for this application. As far as I know, WER handles the crash for all applications that are not .NET or do not have their own crash handler.
In the second screenshot, the 3rd file is a hdmp file. This is a full dump file generated by WER that you can analyze with windbg.
More information on analyzing user mode dumps in WinDBG is located on this MSDN link:
https://msdn.microsoft.com/en-us/library/windows/hardware/ff538058%28v=vs.85%29.aspx
Also, if you want to change the defaults for WER, you can alter these reg keys described here: https://msdn.microsoft.com/en-us/library/windows/desktop/bb787181%28v=vs.85%29.aspx
I am trying to debug my game in logcat but when I add the script debugger in the build settings my logcat gets flooded with profiler is only supported in Unity Pro.. Since I'm not using the profiler and only use the Google Play Services as a 3th party script I suspect it of starting the profiler.
If so, how do I turn that off so I can debug properly? If not, what else could it be?
I have been trying to filter the text message profiler is only supported in Unity Pro. out of logcat but without success. I'm using the UI monitor.bat in the tools map that come with the Android-SDK. This should be a workaround.
According to the documentation: http://docs.unity3d.com/Manual/Profiler.html - the profiler is a Pro only feature.
The profiler is different from the debug log messages.
To get debug messages out of my app, I call Debug.Log("....") in my scripts, and just run adb logcat and the messages show up:
I/Unity (12241): Status Update: Starting sign-in...
I've associated my Windows 8 App with a file type. However when I open that file my app starts to open and then crashes.
I can't figure out a way to do this while the debugger is attached.
I assume there is something wrong with my OnFileActiavted method so I've resorted to changing random bits of code in that method. This isn't working, so I'm wondering how I should debug this problem.
Does this work? You can debug without launching the app immediately. You can also debug other people's apps.
Another approach:
Debugger.Launch();
When your app starts and execution reaches this line, your app will be stopped and VS will ask if you want to attach a debugger.
Hello I am working windows phone 7 and my application is working perfectly fine into the emulator, but once I start my application into the device it will crashing so how I track the error log into my device.?
how I can check error stack into my device.?
Have a look at LittleWatson. It allows you to get exception information emailed to you from a real device.
It's easy to modify to add extra logging information if you need it to.