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

[Adam Megacz]

"Boehm, Hans" <hans_boehm@hp.com> writes:
> Unfortunately, I think you understand correctly.  Can you try taking
> out the conditional ABORT, and verify that does the right thing?
> That was my mistake in translating the patch from my tree.

Tested and running as build 0218 on xwt.org. It works.

Ok to commit to branch?

  - a

2002-06-02 Adam Megacz <adam@xwt.org>

        * Removed extraneous ABORT()

Index: win32_threads.c
===================================================================
RCS file: /cvs/gcc/gcc/boehm-gc/win32_threads.c,v
retrieving revision 1.9.2.2
diff -u -r1.9.2.2 win32_threads.c
--- win32_threads.c     29 Jun 2002 17:29:51 -0000      1.9.2.2
+++ win32_threads.c     2 Jul 2002 18:10:02 -0000
@@ -134,10 +134,7 @@
                                (LPCONTEXT)&thread_table[i].context))
          ABORT("GetThreadContext failed");
 #      ifdef I386
-         if (thread_table[i].context.Esp >= (DWORD)thread_table[i].stack
-             || thread_table[i].context.Esp < (DWORD)bottom)
-             ABORT("Thread stack pointer out of range");
-         GC_push_one ((word) thread_table[i].context.Edi);
+             GC_push_one ((word) thread_table[i].context.Edi);
          GC_push_one ((word) thread_table[i].context.Esi);
          GC_push_one ((word) thread_table[i].context.Ebp);
          GC_push_one ((word) thread_table[i].context.Ebx);


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