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=75119 --- shadow/75119 2005-06-02 07:07:34.000000000 -0400 +++ shadow/75119.tmp.9599 2005-06-02 07:36:27.000000000 -0400 @@ -1,14 +1,14 @@ Bug#: 75119 Product: Mono: Runtime Version: 1.1 -OS: +OS: unknown OS Details: Status: NEW Resolution: -Severity: +Severity: Unknown Priority: Blocker Component: GC AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] QAContact: [EMAIL PROTECTED] TargetMilestone: --- @@ -45,6 +45,21 @@ Anyhow - FWIW, this works for me, YMMV, the GC is already a mess etc. ;-) ------- Additional Comments From [EMAIL PROTECTED] 2005-06-02 07:07 ------- Created an attachment (id=15251) patch for the GC to handle unknown threads more sensibly + +------- Additional Comments From [EMAIL PROTECTED] 2005-06-02 07:36 ------- +and of course, the GC has changed slightly since I hacked this up so +we need an extra: + +# if defined(THREAD_LOCAL_ALLOC) && !defined(DBG_HDRS_ALL) + LOCK(); + GC_init_thread_local(me); + UNLOCK(); +# endif + +at the tail of GC_thread_register_foreign + +And I'm still getting crashes in the GC - it seems clear we'll have to +de-register thread stacks on destruction; surely. hmm. _______________________________________________ mono-bugs maillist - [email protected] http://lists.ximian.com/mailman/listinfo/mono-bugs
