On Tuesday 21 July 2009 11:29:10 am Kamigishi Rei wrote: > John Baldwin wrote: > > v didn't change, it was always the busted value. Somehow mtx_lock was > > corrupted to the value 0x14ee000 perhaps due to a buffer overflow bug or > > something else. > > > I see; I'll try to track where exactly it becomes corrupted, then. > Thanks for the input. > (Then, I suppose, this corruption remains in the seemingly 'fixed' > revisions as it's probably just padded somewhere.) > > Please forgive my lack of knowledge in concurrent execution related stuff. No problem it can be rather confusing. :) -- John BaldwinReceived on Tue Jul 21 2009 - 13:34:27 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:39:52 UTC