From: erik quanstrom <quanstro@labs.coraid.com>
To: 9fans@9fans.net
Subject: Re: [9fans] 9vx still crashing
Date: Sun, 6 Jun 2010 10:45:06 -0400 [thread overview]
Message-ID: <36db5c71a16e0c5d0b42d6763e9f61b7@coraid.com> (raw)
In-Reply-To: <AANLkTin7sL44HxJnmv0kOX2hFBjzWiDaa-MSRAzH6VOb@mail.gmail.com>
> On Sun, Jun 6, 2010 at 3:16 AM, EBo <ebo@sandien.com> 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
prev parent reply other threads:[~2010-06-06 14:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-06 10:16 EBo
2010-06-06 14:31 ` ron minnich
2010-06-06 14:45 ` erik quanstrom [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=36db5c71a16e0c5d0b42d6763e9f61b7@coraid.com \
--to=quanstro@labs.coraid.com \
--cc=9fans@9fans.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).