[Bug 224818] RC4: Installation bails out with "cannot start novell-zmd" even though zmd is up and running
https://bugzilla.novell.com/show_bug.cgi?id=224818 ------- Comment #34 from nabhishek@novell.com 2006-12-01 02:43 MST ------- The signal handler's only purpose in rug was to kill the process. This can be removed but it does not seem to be responsible for the hang. The only possible cause seems to be the changes made to mono-core. Looking at Miguel's patch (bug 221277), the new locking which was introduced could be the issue. Can someone who knows mono look at this snippet of the patch? The unlock seems to happen only in the conditional and not outside, was that intentional? diff -ru /tmp/mono-1.1.18/mono/metadata/metadata.c metadata/metadata.c --- /tmp/mono-1.1.18/mono/metadata/metadata.c 2006-10-12 20:16:07.000000000 +0200 +++ metadata/metadata.c 2006-12-01 01:14:19.000000000 +0100 @@ -1490,6 +1490,7 @@ int count = 0; gboolean found; + mono_loader_lock (); /* * According to the spec, custom modifiers should come before the byref * flag, but the IL produced by ilasm from the following signature: @@ -1561,6 +1562,7 @@ if (!do_mono_metadata_parse_type (type, m, container, ptr, &ptr)) { if (type != &stype) g_free (type); + mono_loader_unlock (); return NULL; } -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
participants (1)
-
bugzilla_noreply@novell.com