Notice (2018-05-24): bugzilla.xamarin.com is now in
Please join us on
Visual Studio Developer Community and in the
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
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.
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.
Created attachment 5544 [details]
Another launch attempt (--trace=wrapper)
Ah, one perhaps very import thing to mention as well:
In the console, it says "Memory access error", followed by a silent mono crash.
DO you have the actual crash trace?
From Monodevelop? - Or from gdb?
Or from the place where the exception occurs?
The log file should contain a gdb backtrace.
Created attachment 5549 [details]
make run log
This should rather be more interesting than a gdb dump.
It doesn't like look like a crash, rather an unhandled exception at startup.
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?
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!