[Mono-bugs] [Bug 340899] New: System.Threading.Thread.Join_internal -> point should not be reached

bugzilla_noreply at novell.com bugzilla_noreply at novell.com
Sat Nov 10 17:39:27 EST 2007


           Summary: System.Threading.Thread.Join_internal -> point should
                    not be reached
           Product: Mono: Class Libraries
           Version: 1.2
          Platform: PowerPC
        OS/Version: Mac OS X 10.5
            Status: NEW
          Severity: Major
          Priority: P5 - None
         Component: System
        AssignedTo: mono-bugs at ximian.com
        ReportedBy: alwin at majic-12.nl
         QAContact: mono-bugs at ximian.com
          Found By: ---

Created an attachment (id=182924)
 --> (https://bugzilla.novell.com/attachment.cgi?id=182924)
nant patch for gendarme

situation :

i'm porting gendarme to nant, while doing this i got internal
threading/compiler errors.
i'm running osx 10.5 (problem also exitsts on 10.4). and the 1.2.1 release of
if i'm reading the error correctly code is executed which should not reached
under any circumstance.

error description :

** ERROR **: file mini-ppc.c: line 1937 (ppc_patch): should not be reached

this seems to be a framework or compiler error.

how to reproduce :

take the gendarme sourcecode from svn, and apply the attached patch. 
after that type nant en watch the error.
(also any feedback about the gendarme stuff is welcome ;))

the stacktrace is as follows :

 at (wrapper managed-to-native) System.Threading.Thread.Join_internal
(int,intptr) <0xffffffff>
  at (wrapper managed-to-native) System.Threading.Thread.Join_internal
(int,intptr) <0x00094>
  at System.Threading.Thread.Join () <0x0002c>
  at NUnit.Core.TestRunnerThread.Wait () <0x0007c>
  at NUnit.Core.ThreadedTestRunner.Wait () <0x0005c>
  at NUnit.Core.ThreadedTestRunner.EndRun () <0x0002c>
  at NUnit.Core.ThreadedTestRunner.Run (NUnit.Core.EventListener,string[])
  at NUnit.Core.ProxyTestRunner.Run (NUnit.Core.EventListener,string[])
  at NUnit.Core.RemoteTestRunner.Run (NUnit.Core.EventListener,string[])
  at NUnit.Core.ProxyTestRunner.Run (NUnit.Core.EventListener) <0x0003c>
  at (wrapper xdomain-dispatch) NUnit.Core.ProxyTestRunner.Run
(object,byte[]&,byte[]&) <0x002c4>
  at (wrapper xdomain-invoke) NUnit.Core.ProxyTestRunner.Run
(NUnit.Core.EventListener) <0x001fc>
  at NAnt.NUnit2.Tasks.NUnit2Task.ExecuteTask () <0x008e4>
  at NAnt.Core.Task.Execute () <0x001f4>
  at NAnt.Core.TaskContainer.ExecuteChildTasks () <0x0027c>
  at NAnt.Core.TaskContainer.ExecuteTask () <0x00024>
  at NAnt.Core.Task.Execute () <0x001f4>
  at NAnt.Core.Tasks.LoopTask.ExecuteChildTasks () <0x00070>
  at NAnt.Core.TaskContainer.ExecuteTask () <0x00024>
  at NAnt.Core.Tasks.LoopTask.DoWork (string[]) <0x001dc>
  at NAnt.Core.Tasks.LoopTask.ExecuteTask () <0x01138>
  at NAnt.Core.Task.Execute () <0x001f4>
  at NAnt.Core.Target.Execute () <0x00318>
  at NAnt.Core.Project.Execute (string,bool) <0x00130>
  at NAnt.Core.Project.Execute () <0x004b4>
  at NAnt.Core.Project.Run () <0x003b0>
  at NAnt.Core.ConsoleDriver.Main (string[]) <0x013e4>
  at (wrapper runtime-invoke)
(object,intptr,intptr,intptr) <0x00074>
  at (wrapper managed-to-native) System.Reflection.MonoMethod.InternalInvoke
(object,object[]) <0xffffffff>
  at (wrapper managed-to-native) System.Reflection.MonoMethod.InternalInvoke
(object,object[]) <0x00094>
  at System.Reflection.MonoMethod.Invoke
  at System.Reflection.MethodBase.Invoke (object,object[]) <0x00040>
  at HelperArguments.CallConsoleRunner () <0x004ec>
  at (wrapper delegate-invoke) System.MulticastDelegate.invoke_void ()
  at System.AppDomain.DoCallBack (System.CrossAppDomainDelegate) <0x00038>
  at (wrapper remoting-invoke-with-check) System.AppDomain.DoCallBack
(System.CrossAppDomainDelegate) <0x000a8>
  at NAnt.Console.ConsoleStub.Main (string[]) <0x00ff0>
  at (wrapper runtime-invoke)
(object,intptr,intptr,intptr) <0x00074>

Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
You are the assignee for the bug.

More information about the mono-bugs mailing list