Please do not reply to this email- if you want to comment on the bug, go to the URL shown below and enter your comments there.
Changed by [EMAIL PROTECTED] http://bugzilla.ximian.com/show_bug.cgi?id=75387 --- shadow/75387 2005-06-27 08:02:33.000000000 -0400 +++ shadow/75387.tmp.2222 2005-06-29 19:45:45.000000000 -0400 @@ -31,6 +31,27 @@ at least 8 signals. ------- Additional Comments From [EMAIL PROTECTED] 2005-06-27 05:36 ------- Created an attachment (id=15386) sigrtmin.diff + +------- Additional Comments From [EMAIL PROTECTED] 2005-06-29 19:45 ------- +I would rather have some way of testing for this than mkaing the +change on every distribution. + +This patch only turns the problem into a potentially different problem. + +What we probably need to have is a way of "probing" if these signals +are being used, something like this: + +handler = -1; +for (int i = SIGRTMIN; i < SIGRTMAX; i++){ + sigaction (i, NULL, &old); + if (old.sa_handler == NOT_SET){ + handler = i; break; + } +} + +Now, the above only works if signals have been preset before Mono has +been invoked. Am not sure if there is a reliable way of coping with +this problem _______________________________________________ mono-bugs maillist - [email protected] http://lists.ximian.com/mailman/listinfo/mono-bugs
