From: Philippe Anel <xigh@bouyapop.org>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] 9vx, kproc and *double sleep*
Date: Fri, 11 Jun 2010 20:51:03 +0200 [thread overview]
Message-ID: <4C128597.2080204@bouyapop.org> (raw)
In-Reply-To: <20100611183405.831205B8B@mail.bitblocks.com>
You can download my own (ugly) 9vx source code here :
http://www.bouyapop.org/9vxigh.tar.bz2
In 9vx you'll find .gdbinit and crash.c.
Just copy it to vx32 and replace 9vx folder, compile it and execute it
under gdb with you own 9vx env.
(gdb) r -F -r <your folder>
then compile and execute crash.c with 8c/8l.
When it crashes, you can watch the latest logs with the gdb command
k9logs 100 (it will show you 100 last ops).
Phil;
Bakul Shah wrote:
> On Fri, 11 Jun 2010 19:31:58 +0200 Philippe Anel <xigh@bouyapop.org> wrote:
>
>> I only did my tests on 9vx. I have a version that I instrumented with
>> a circular log buffer, and I have some gdb macros which dumps the
>> buffer.
>>
>> I can put the whole source somewhere and even a log with my comments
>> of the bug if you want to see it. But please note that I made several
>>
>
> Yes, please. Thanks!
>
>
>> changes (because I had to understand how it works) and I would rather
>> copy my changes to the latest 9vx source tree so that everyone can
>> read it. What do you think ?
>>
>
> Agreed. Best to check this in on a separate branch though.
> Branching/merging is cheap in hg.
>
>
>> Please, I would like to insist on the fact I'm not saying the promela
>> model is wrong. And I realize that the fix I propose might not be the
>> good one. Maybe the problem is even elsewhere. All these is just
>> feelings, logs and headache.
>>
>
> I haven't used promela so can't say anything about it.
> sleep() is pretty complicated so figuring it out will take
> some time and effort but I first have to understand the cause
> and from past experience I know that code to check a cause
> hypothesis can be quite valuable (hence my earlier question).
> An unambiguous proof of what went wrong somehow frees my mind
> to better focus on the solution!
>
> Thanks for your thought experiements & code!
>
>
>
next prev parent reply other threads:[~2010-06-11 18:51 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-11 14:06 Philippe Anel
2010-06-11 14:40 ` ron minnich
2010-06-11 14:49 ` erik quanstrom
2010-06-11 14:54 ` Philippe Anel
2010-06-11 15:03 ` erik quanstrom
2010-06-11 15:22 ` Philippe Anel
2010-06-11 15:25 ` Philippe Anel
2010-06-11 14:59 ` Philippe Anel
2010-06-11 17:11 ` Bakul Shah
2010-06-11 17:31 ` Philippe Anel
2010-06-11 18:34 ` Bakul Shah
2010-06-11 18:36 ` erik quanstrom
2010-06-11 18:51 ` Philippe Anel [this message]
2010-06-12 7:02 ` Philippe Anel
2010-06-12 9:22 ` Philippe Anel
2010-06-12 11:51 ` erik quanstrom
2010-06-13 13:01 ` Richard Miller
2010-06-13 13:43 ` Philippe Anel
2010-06-13 14:26 ` Philippe Anel
2010-06-13 16:20 ` ron minnich
2010-06-13 16:34 ` Philippe Anel
2010-06-13 17:23 ` Philippe Anel
2010-06-13 18:03 ` Philippe Anel
2010-06-14 19:15 ` Charles Forsyth
2010-06-14 19:36 ` Philippe Anel
2010-06-15 2:57 ` ron minnich
2010-06-15 3:36 ` ron minnich
2010-06-12 20:15 ` Richard Miller
2010-06-12 20:30 ` ron minnich
2010-06-12 22:15 ` Charles Forsyth
2010-06-13 0:04 ` ron minnich
2010-06-13 13:32 ` erik quanstrom
2010-06-13 22:34 ` Charles Forsyth
2010-06-13 9:00 ` Richard Miller
2010-06-11 14:49 ` Philippe Anel
2010-06-11 14:59 ` ron minnich
2010-06-11 15:02 ` ron minnich
2010-06-11 15:04 ` erik quanstrom
2010-06-11 15:43 ` ron minnich
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=4C128597.2080204@bouyapop.org \
--to=xigh@bouyapop.org \
--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).