[Gc] Back to "GC Stack problem on Win32" - refinement
hans.boehm at hp.com
Sat Feb 28 15:32:41 PST 2009
Thanks. I committed something very similar to that patch for now. All indications so far are that my problems are unrelated to the patch.
I'll see if I can track down what's going on. It may be a GetWriteWatch issue with incremental GC.
> -----Original Message-----
> From: gc-bounces at napali.hpl.hp.com
> [mailto:gc-bounces at napali.hpl.hp.com] On Behalf Of Ivan Maidanski
> Sent: Friday, February 27, 2009 10:48 AM
> To: gc at napali.hpl.hp.com
> Subject: Re: [Gc] Back to "GC Stack problem on Win32" - refinement
> "Boehm, Hans" <hans.boehm at hp.com> wrote:
> > I've had a patch (attached, against CVS) in my tree for a
> while that I
> > think started with Ivan's diff36 and diff37, and then made
> yet another
> > attempt to restructure the surrounding code. (Diff36 and
> diff37 are
> > Ivan's originals.)
> > My concern is that I've been seeing occasional failures,
> particularly with the win32 (32 bit) version
> (NT_STATIC_THREADS_MAKEFILE) after applying this patch. (I'm
> compiling with VS2005.) It's possible that these failures
> existed all along. But they look like either a piece of the
> stack or some relevant registers are not getting scanned.
> The failure seems to occur without triggering any assertion
> failures, even after adding the fairly expensive assertion
> here. They seem to generally occur in reverse_test, but may
> occur during manipulation of data referenced only by the
> stack. Static root finding doesn't seem to be the issue.
> > Has anyone else still been seeing intermittent failures on win32?
> > ...
> > Hans
> I don't observe any test.c failures with CVS [+
> win32_threads.c.diff] compiled with VC++ 2005/2008
> Gc mailing list
> Gc at linux.hpl.hp.com
More information about the Gc