Hi,
it was a Gtk# threading issue, which is now resolved. Everything works
surprisingly good now on the mono side.
I'm wondering, gtk is a native api, but it would make sense to encapsulate
errors in exceptions.
Is this just missing or by design?
Thanks,
Matthias
On Sat, Jul 14, 2012 at 2:33
Gtk is not a thread-safe toolkit. Once you start accessing it in a
multi-threaded way you run the risk of corrupting state so badly that
the entire application blows up. A regular gtk error is converted to a
regular .NET exception, but memory corruption such as this will always
lead to your app
Hey,
like I said I'm trying to port a Application to mono, now I'm experiencing
a mono SIGSEGV:
To reproduce the issue type (mono installed and in PATH):
git clone git://github.com/matthid/synclib.git
cd synclib
git checkout -b devel remotes/origin/devel
export FSC=mono
