Now open the project you want to valgrind, and set the VALGRIND environment variable to the command to execute to use valgrind:

Run (not debug) your project. You will see this in the Application Output:

In particular read the second line, you need to do exactly as it says: use gdb to attach to the app and then detach again. Once you've done this the app should start up (slowly, Valgrind makes your app a lot slower). Quite much output is printed to the Application Output, most of it is just noise though.

The messages you should be looking for (if you're trying to figure out why your app is crashing), are:

Invalid read of size X

Invalid write of size X

You can try to track down the reason for the following messages if you're just trying to find out why the app behaves strangely. Just have in mind that most of these messages are harmless, it can be due to "smart" optimizations in the code or by the compiler which valgrind doesn't understand.

Conditional jump or move depends on uninitialised value(s)

Use of uninitialised value of size X

For a thorough explanation of all these messages from Valgrind you should read their documentation.

Some of this information should also (but probably won't since that's the problem you're trying to solve in the first place) show up in MonoDevelop's Application Output pad (everything after the 'connect output' line, since that's when the app's standard output is redirected to MonoDevelop):

Thursday, May 31, 2012

This is mostly for myself so these ideas aren't lost in bugzilla comments or GMail's bottomless mail pit.

How to create a crash report when the app is hung

Update

There is a much easier way to do this. All iOS versions and devices include a way to force quit an application:

Hold down the On/Off button until "slide to power off" appears.

Release the On/Off button.

Hold down the Home button.

After a few seconds the app will be terminated, and a crash report will be generated (the app's exception code will be 0xdeadfa11).

This snippet will cause the app to generate a crash report after 30 seconds (feel free to modify the timeout to ensure it only crashes after you've managed to hang the app).

Once the app has crashed, you should get a crash report in Xcode, hopefully with stack traces giving some clues as to what the app was trying to do when it hung. If you can't make heads and tails of the crash report, you should file a bug (remember to attach the crash report!).

Just replace the Application class in Main.cs with this (if you've made modifications to the Main.cs file yourself, you'll have to modify this code accordingly).

Next tip will go here next time I remember something I don't want to forget again

Saturday, April 14, 2012

If you use MonoTouch a bit, you will once in a while run into native crashes. In a perfect world you'd never see such a horrible thing, but unfortunately the world isn't perfect, and in real life there are several ways you can end up crashing your app. Usual debugging techniques with MonoDevelop will not work, but with some ingenuity you can figure out what's going on. And you will catch a glimpse of how the world is for those poor guys who can't develop in C#!

Now, how do you find out what happened? You need as much information as possible, and information related to a native crash is twofold:

Crash report.

Console output.

Where you can find each differs depends on whether you're running in the iOS simulator or on an iOS device.

You're running in the iOS simulator.

In this case, the console is the system console on your Mac. You can find the Console application in Applications -> Utilities -> Console. This is how it looks like:

Now let's see what happens if you crash in the simulator. You will get this dialog:

and if you click the Report button, you'll see the crash report:

The same crash report is also available in the Console, in case you dismissed the dialog:

You're running on an iOS device.

In this case, you want Xcode's Organizer. Open Xcode, and go to the Window -> Organizer menu entry.

Here you will find crash reports under the Device Logs node, and the obviously the console output will be under the Console node.

Now what?

Some times the information you found tells you exactly what happened.

This is the case for an unhandled exception, in which case you'll see something like this in the console:

in this case it's pretty obvious what happened. But this isn't often the case, usually the information is at best unfamiliar unless you already have experience debugging native crashes (and in some cases the crash happens way after the underlying cause, and any relevant information is long lost. When this happens you'll have to resort to more creative debugging techniques).

I will write more blog posts describing some of the most common reasons for native crashes later, but in the mean time you have a few options to get help:

In all cases be sure to include all information you're able to gather, have in mind that even though the console output and crash reports may be greek to you, it may provide valuable information to somebody else.