Bug 16455 - Monodevelop 4.2 (master) crashes on Linux >3.10 x64
Summary: Monodevelop 4.2 (master) crashes on Linux >3.10 x64
Alias: None
Product: Runtime
Classification: Mono
Component: Interop ()
Version: 3.2.x
Hardware: PC Linux
: --- normal
Target Milestone: ---
Assignee: Bugzilla
Depends on:
Reported: 2013-11-26 06:44 UTC by alex
Modified: 2013-11-27 13:20 UTC (History)
3 users (show)

Is this bug a regression?: ---
Last known good build:

The function trace log. (--trace=all) (1.13 MB, application/x-xz)
2013-11-26 06:44 UTC, alex
Another launch attempt (--trace=wrapper) (25.91 KB, application/octet-stream)
2013-11-26 06:48 UTC, alex
make run log (78.70 KB, text/x-log)
2013-11-26 15:38 UTC, alex

Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and Mono organizations on GitHub to continue tracking issues. Bugzilla will remain available for reference in read-only mode. We will continue to work on open Bugzilla bugs, copy them to the new locations as needed for follow-up, and add the new items under Related Links.

Our sincere thanks to everyone who has contributed on this bug tracker over the years. Thanks also for your understanding as we make these adjustments and improvements for the future.

Please create a new report on GitHub or Developer Community with your current version information, steps to reproduce, and relevant error messages or log files if you are hitting an issue that looks similar to this resolved bug and you do not yet see a matching new report.

Related Links:

Description alex 2013-11-26 06:44:37 UTC
Created attachment 5543 [details]
The function trace log. (--trace=all)


Very often (== very unregularly, on some boot sessions it works, then I gotta restart to make it work again) 
I simply can't get neither MonoDevelop nor KeePass to launch properly/regularly.

I ran monodevelop with --trace to have an insight of the method which crashs.. it's always(!) the dup2 method.

The problem occurred ~ a month ago, I always kinda accepted this awkward new circumstance but well, now not anymore.
Comment 1 alex 2013-11-26 06:48:00 UTC
Created attachment 5544 [details]
Another launch attempt (--trace=wrapper)
Comment 2 alex 2013-11-26 06:52:39 UTC
Ah, one perhaps very import thing to mention as well: 
In the console, it says "Memory access error", followed by a silent mono crash.
Comment 3 Mikayla Hutchinson [MSFT] 2013-11-26 15:00:40 UTC
DO you have the actual crash trace?
Comment 4 alex 2013-11-26 15:08:54 UTC
From Monodevelop? - Or from gdb?

Or from the place where the exception occurs?
Comment 5 Mikayla Hutchinson [MSFT] 2013-11-26 15:12:03 UTC
The log file should contain a gdb backtrace.
Comment 6 alex 2013-11-26 15:38:47 UTC
Created attachment 5549 [details]
make run log

This should rather be more interesting than a gdb dump.
Comment 7 Zoltan Varga 2013-11-27 03:48:23 UTC
It doesn't like look like a crash, rather an unhandled exception at startup.
Comment 8 alex 2013-11-27 04:07:42 UTC
But why is this occuring in such an undefined/unforeseeable manner? Without recompiling/moving/copying any binaries, it might work, and in those other couple of times it does not?

Caching, I/O, Ram?
Comment 9 alex 2013-11-27 13:20:41 UTC
Okay, the program does not seem to be located in mono - so far.

Somehow, I can't execute monodevelop via a terminal, an XFCE launcher nor gdb - but via a makefile!

Running make run inside my local MD clone repo does not cause any kind of problem. Anyway, thanks for your help!