                                                                                                                                                                                                                                                                
Newsgroups: perl.perl6.internals
Path: archiver1.google.com!news2.google.com!news.maxwell.syr.edu!newsfeed.stanford.edu!nntp.perl.org
Mailing-List: contact perl6-internals-h...@perl.org; run by ezmlm
Message-ID: <404D8D7E.4050306@toetsch.at>
Date: Tue, 09 Mar 2004 10:25:18 +0100
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.4) Gecko/20011129
MIME-Version: 1.0
To: P6I <perl6-intern...@perl.org>
Subject: 2 more DOD bugs fixed
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Approved: n...@nntp.perl.org
From: l...@toetsch.at (Leopold Toetsch)

1) singleton PMCs like Random or Env got destroyed during DOD runs
2) and a really nasty one:
During (overridden vtable) method calls, the caller doesn't know that a 
method is called, so the return continuation in P1 wasn't preserved in 
the context - the caller just assumes, that its preserved. Now when a 
method calls another sub or method, a new return continuation is created 
in P1, which unachored the previous one - it got destroyed during a DOD 
run. A DOD run is easily triggered during tracing, so this matches the 
symptoms of recently reported DOD bugs.

Jens Rieks had mailed me his EBNF parser some time ago, which happend to 
expose that bug. After ++some hours, I could eventually nail it down to 
what is now t/op/gc_10.pasm.

leo