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=82490 --- shadow/82490 2007-08-20 07:49:10.000000000 -0400 +++ shadow/82490.tmp.24849 2007-08-20 08:10:12.000000000 -0400 @@ -1,15 +1,15 @@ Bug#: 82490 Product: Mono: Runtime Version: 1.2 -OS: unknown -OS Details: -Status: RESOLVED -Resolution: NOTABUG +OS: GNU/Linux [Other] +OS Details: amd64 +Status: REOPENED +Resolution: Severity: Unknown -Priority: Normal +Priority: Minor Component: remoting AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] QAContact: [EMAIL PROTECTED] TargetMilestone: --- URL: @@ -149,6 +149,21 @@ ------- Additional Comments From [EMAIL PROTECTED] 2007-08-20 07:49 ------- This is by design and it happens to match MS.NET as well. [ContextStatic] has the same semantic like [ThreadStatic], which means that the field gets initialized only once. + +------- Additional Comments From [EMAIL PROTECTED] 2007-08-20 08:10 ------- +Thanks for clarification, but there is still a related bug. Notice the +initialization of static variable 'foo' - it was not initialized +before first use, but later: + +C foo:1 goo:0 ctxid:1 <- foo should be initialized to 8 (and ++ed to 9) +F foo:8 goo:0 ctxid:1 + +It seems that problem happens only during first initialization of +ContextStatic variable. + +Lowering priority, as this happens only when using initializers with +[ContextStatic] which has quite unusable semantic. + _______________________________________________ mono-bugs maillist - [email protected] http://lists.ximian.com/mailman/listinfo/mono-bugs
