From mboxrd@z Thu Jan 1 00:00:00 1970 From: erik quanstrom Date: Sun, 6 Jun 2010 10:45:06 -0400 To: 9fans@9fans.net Message-ID: <36db5c71a16e0c5d0b42d6763e9f61b7@coraid.com> In-Reply-To: References: <07ff4890a9498d620fbabf8df150225a@swcp.com> MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 8bit Subject: Re: [9fans] 9vx still crashing Topicbox-Message-UUID: 2fdbbdee-ead6-11e9-9d60-3106f5b1d025 > On Sun, Jun 6, 2010 at 3:16 AM, EBo wrote: > > > > I'm still having 9vx crash even after removing -O3 from the build flags. > > An odd error that pops up randomly in rio (not in the terminal window) is > > "double sleep called from...".  Thought this tidbit might be useful to the > > discussion of what might be going on... > > I'm pretty sure it's memory corruption. i assume you mean 9vx is scribbling on memory it shouldn't, not that there is a hardware bug. when i've seen this in plan 9, i haven't ever found it to be a wild pointer. it's always been. - stack > 4k, - a missing waserror()/poperror() around a sleep, - locking bugs. while it certainly could be a wild poointer, it doesn't smell like that to me. where (file/line) is the double sleep occuring? that could be a clue. remember addresses from acid aren't much help unless one has the exact same binary. - erik