All geek questions in one place

SIGABRT error when starting MonoTouch application

I'm new to MonoTouch and more than ever when I try to run the MonoTouch application on the iPhone simulator (debug mode and normal), I get a long error output that starts with the following message:

Connection error stdout and stderr (127.0.0.1:10001) Failed to register com.yourcompany. [Appnamehere] with boot server. Error: unknown error code. This usually means that another instance of this process is already running or is in the debugger. Stacktrace:

at (wrapper managed-to-native) MonoTouch.UIKit.UIApplication.UIApplicationMain (int, string [], intptr, intptr) <0x00004> at (wrapper managed-to-native) MonoTouch.UIKit.UIApplication.UIApplicationMain (int, string [], intptr, intptr) <0x00004> in MonoTouch.UIKit.UIApplication.Main (line [], line, line) <0x00089> in MonoTouch.UIKit.UIApplication.Main (line []) <0x00014> in PodcastManager.Application .Main (string []) <0x00010> at (runtime-invoke shell) .runtime_invoke_void_object (object, intptr, intptr, intptr) <0x00043>

And ends:

==================================================== ================

Got SIGABRT while executing native code. This usually indicates a fatal error in the mono executable version or one of the built-in libraries used by your application.

==================================================== ================

It is strange that this will work for a while. Once rebooting my machine did this. Others, just restarting MonoDevelop and / or the simulator.

I can provide all the error output if you think it can help.

Any ideas?

+4
source share
3 answers

- Update - after updating to 2.0.2 I did not see this problem.

After playing with her for a long time and meeting this error report , I came to the conclusion that until he finds a way to prevent this error, NEVER stop the debugging session in the IDE. If you stop the debugging session when the code is not at the breakpoint by clicking the home button, you will see that you will avoid this situation.

+1
source

This is a problem with the monotouch debugger. Sometimes, when an application crashes, the debugger freezes in memory, and this prevents the application from starting again. As you said, sometimes closing MonoDevelop and the simulator is enough to clear the debugger, sometimes you need a full reboot. It is also an experience that I have, which is probably the only thing that I have discovered with a monotone so far.

Many times I can directly kill a process from the console. To do this, open the console and enter "top". You will see a list of processes that use most of the memory, your application will probably be on top using almost 100% of the processor. Save the identifier of this line and enter q to exit. Now enter "kill -9 ???" Where??? This is the identifier you received from above.

Monotouch 2.0 fixed many of these problems, if you haven’t updated yet, I would seriously recommend that you do this. I am launching beta channel 2.0, and its LOT is more stable. Battles were reduced from 1 or 2 every hour to 1 or 2 per day. This still happens, unfortunately.

+3
source

I think this error occurs when any native monotouch library is missing. This is due to the removal of Visual Studio or Update Xamarin. I encountered the same error and allowed Unistalland to reinstall Xamarin Visual Studio and Xamarin Studio. It takes 10 minutes and all problems are resolved.

0
source

Source: https://habr.com/ru/post/1306359/

More articles:


All Articles