[M3devel] thread alert problem on NT386

Randy Coleburn rcoleburn at scires.com
Thu Jun 12 07:04:57 CEST 2008

Thanks.  I've solved the problem.  It wound up being my fault.

>>> Tony Hosking <hosking at cs.purdue.edu> 6/11/2008 11:35 PM >>>
Jay will need to track this one.  I've barely ever touched ThreadWin32.

On Jun 12, 2008, at 1:44 AM, Randy Coleburn wrote:

I'm running across a problem on Windows XP using threads.
Specifically, I am getting the following runtime error:
*** runtime error:
***    Thread client error: Alert called from non-Modula-3 thread
***    file "..\src\thread\WIN32\ThreadWin32.m3", line 325
Stack trace:
   FP         PC      Procedure
---------  ---------  -------------------------------
0x5dbfea4   0x5c5e5c  Die + 0x2d in ..\src\thread\WIN32\ThreadWin32.m3
0x5dbfedc   0x5c3acd  Alert + 0x35 in ..\src\thread\WIN32\ThreadWin32.m3
0x5dbff2c   0x403bb1  CloseWindow + 0x185 in ..\src\Main.m3
0x5dbff50   0x4082c3  TaskApply + 0x5b in ..\src\Utils.m3
0x5dbff88   0x5c4a6a  RunThread + 0x1f6 in ..\src\thread\WIN32\ThreadWin32.m3
0x5dbffb4   0x5c4803  ThreadBase + 0x3a in ..\src\thread\WIN32\ThreadWin32.m3
.........  .........  ... more frames ...
Now, I know for a fact that the thread calling Thread.Alert is indeed a modula-3 thread.
Any ideas?

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://m3lists.elegosoft.com/pipermail/m3devel/attachments/20080612/b6b422c8/attachment-0002.html>

More information about the M3devel mailing list