|
From: Tom H. <to...@co...> - 2009-09-07 07:57:43
|
On 04/09/09 23:02, Nicholas Nethercote wrote: > On Sat, Sep 5, 2009 at 2:08 AM, Tom Hughes<to...@co...> wrote: >> >> R --> B1 --> B2 --> B3 --> ... >> | | | >> | | | >> V V V >> I1 I2 I3 >> >> The sequence of events I am seeing for a block in the list (B2 for >> example) when the leak check runs is: >> >> - Interior pointer to B2 found, B2 changed to Possible. >> >> - B2 scanned and pointer to I2 found. I2 marked as Possible >> because B2 is only Possible. >> >> - Start pointer to B2 found and B2 upgraded to Reachable. >> >> Which is where we finish, with B2 Reachable but I2 only Possible... > > Hmm, I can believe that. I don't think I considered the > was-Possible-now-Reachable-so-recategorise-children case. Attached is a simple test case which I've constructed to demonstrate the problem. I'm playing around with some possible fixes now... Tom -- Tom Hughes (to...@co...) http://www.compton.nu/ |