'thread stack pointer out of range'? -- solved?

[Boehm, Hans]

I've attached a patch against the 3.1 tree.  This isn't exactly the patch I received, and it hasn't been tested.  Thus I'd prefer if this had some miles on it before it was checked into the 3.1 tree.  Could you try it? 

I'm also open to opinions about the warning, though I'd love to see a run that generated the warning but didn't fail.

Thanks.

Hans

-----Original Message-----
From: Adam Megacz
To: Boehm, Hans
Cc: ''java@gcc.gnu.org' '
Sent: 6/26/02 12:08 PM
Subject: Re: 'thread stack pointer out of range'? -- solved?

Do you think that you could put this patch into the 3.1.1 branch? It
closes to non-documentation patches in four days.

>From what I can tell, it will solve the problem -- Winsock is using SP
for another stack, not for random data storage. So hard-to-detect
conditions like the SP being off by one should never occur.

  - a

-- 
Sick of HTML user interfaces?
www.xwt.org

"disappointing retail sales figures suggest to some that America's love
 affair with retail therapy may be over."    -- _The Economist_, 19-Jun

-------------- next part --------------
A non-text attachment was scrubbed...
Name: win32_threads.c.diff
Type: application/octet-stream
Size: 1109 bytes
Desc: not available
URL: <http://gcc.gnu.org/pipermail/java/attachments/20020626/5a5896c9/attachment.obj>