[M3devel] Juno/win32threads
Jay K
jay.krell at cornell.edu
Mon Sep 21 22:13:21 CEST 2009
Yes that's what I was referring to.
You were already looking at the right timeframe, around Feb 20 2009.
Earlier mail has a 30 minute window identified.
-Jay
From: hosking at cs.purdue.edu
To: hosking at cs.purdue.edu
Date: Mon, 21 Sep 2009 10:03:32 -0400
CC: m3devel at elegosoft.com; jay.krell at cornell.edu
Subject: Re: [M3devel] Juno/win32threads
P.S. I did commit back some changes to ThreadWin32.m3 which backed out some of 1.30. Did you try those?
On 21 Sep 2009, at 09:53, Tony Hosking wrote:
OK, I've lost track, since we've been discussing two different things: the problems with pthreads which I just fixed, and the Windows threading problem. What is the time-frame that I should be looking at for that problem?
On 21 Sep 2009, at 00:14, jay.krell at cornell.edu wrote:
Eh? Tony, the thread changes from around feb 20 that you recently 'unmerged'? These crashes seem to date from around Feb, more precise info in my other mails..
- Jay (phone)
On Sep 20, 2009, at 7:04 PM, Tony Hosking <hosking at cs.purdue.edu> wrote:
I don't think anything I changed affects Windows.
On 19 Sep 2009, at 23:24, Jay K wrote:
Tony, the behavior still seems the same.
(a74.f50): Access violation - code c0000005 (first chance)
First chance exceptions are reported before any exception handling.
This exception may be expected and handled.
eax=00000000 ebx=00000000 ecx=7ffdf000 edx=00e29620 esi=0128872c edi=00200000
eip=005eb75d esp=0012f940 ebp=0012f95c iopl=0 nv up ei pl zr na pe nc
cs=001b ss=0023 ds=0023 es=0023 fs=003b gs=0000 efl=00010246
m3core!Thread__Join+0x14b:
005eb75d 8b5ffc mov ebx,dword ptr [edi-4] ds:0023:001ffffc=????????
0:000>
0:000> r edi
edi=00200000
Can you maybe debug this on birch?
I can e.g. put debuggers at \bin\x86\cdb
(just install them locally which involves some GUI, then tar/gz them up and untar/gz..you don't need the installer to run, can just copy them around)
and then you can like:
ssh hudson at birch.elegosoft.com
ssh elego at localhost2
/cygdrive/c/bin/x86/cdb ./Juno.exe
Just be sure not to run Juno outside of a debugger..not sure what will happen, but you won't be able to see it.
Or, feel free to commit some version that uses RTIO a bunch and I can send you the output.
Slow turnaround that way.
Clearly nobody is using any of this stuff..
- Jay
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://m3lists.elegosoft.com/pipermail/m3devel/attachments/20090921/5951a5da/attachment-0002.html>
More information about the M3devel
mailing list