[Issue 72] valgrind: use of unitialized values in the gcx module

[d-bugmail at puremagic.com]

http://d.puremagic.com/issues/show_bug.cgi?id=72


Brad Roberts <braddr at puremagic.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |braddr at puremagic.com


--- Comment #6 from Brad Roberts <braddr at puremagic.com> 2010-11-07 14:49:08 PST ---
I looked at this one a long time ago.  I think it should be closed as won't
fix.  The problem, as I remember it, is that the gc walks the stack.  The stack
isn't fully dense, so there's blocks in it that have never had a value
assigned.  So, when the gc walks those blocks it complains that their values
are indeterminate.

Two ways to fix it, that I can see:
  1) always initialize empty stack slots -- cost performance
  2) teach the gc to be precise about it's stack scanning -- complex

-- 
Configure issuemail: http://d.puremagic.com/issues/userprefs.cgi?tab=email
------- You are receiving this mail because: -------