[Mono-dev] GLib's GModule + libmono = segfault?

[Ivan N. Zlatev]

Hi,

I am experiencing a strange problem here. I have a library "A" that
g_module_opens ("B"). "B" embeds mono and does mono initialization. If
I try to do g_module_close ("B")  it SEGFAULTS with the following
stacktrace:

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread -1234973792 (LWP 6406)]
0xb6e96934 in ?? ()

0xb7f4f3a6 in _dl_catch_error () from /lib/ld-linux.so.2
0xb7327ee4 in dlclose_doit () from /lib/libdl.so.2
#0  0xb7f54093 in _dl_close () from /lib/ld-linux.so.2
#1  0xb7327ee4 in dlclose_doit () from /lib/libdl.so.2
#2  0xb7f4f3a6 in _dl_catch_error () from /lib/ld-linux.so.2
#3  0xb73282fc in _dlerror_run () from /lib/libdl.so.2
#4  0xb7327f1a in dlclose () from /lib/libdl.so.2
#5  0xb750022a in _g_module_close (handle=0xb7f5d6c4, is_unref=0) at
gmodule-dl.c:133
#6  0xb750036e in g_module_close (module=0x810fe20) at gmodule.c:537

This happens both if libmono is dynamically or statically linked, but
does *not* happen if I remove the mono part in "B".

Any thoughts on why is this happening? (Mono SVN HEAD)

-- 
Ivan N. Zlatev

Web: http://www.i-nZ.net
GPG Key: http://files.i-nZ.net/i-nZ.asc
"It's all some kind of whacked out conspiracy."