From: "Russ Cox" <rsc@plan9.bell-labs.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Channel casting
Date: Fri, 23 May 2003 10:10:44 -0400 [thread overview]
Message-ID: <5b2174369b9c532c6b867044a5ae75b5@plan9.bell-labs.com> (raw)
In-Reply-To: <acaeb56e4e92bdf373be0adce75ea8c4@granite.cias.osakafu-u.ac.jp>
> Actually, I couldn't poit out what is really the problem in our marsv.
> It looks like we have no problem, however, sometime it hanged up,
> or depends on the speed of CPU etc. Then, I decided to use buffered
> channel to avoid this... I know it's not a very right solution, however,
> we couldn't live with this buffered channel. If you want to see our
> problem, you can find out it from our sources of marsv where we used
> a buffered channel, which I didn't want of course.
It sounds like you have a simple deadlock. If you put
the unbuffered channel back and then wait for it to
hang, you can inspect the process with
acid -l thread pid
threads()
to get a list of what each thread is doing. If you look
at the ones sending or receiving, you should be able to
work out why the deadlock happens.
Russ
prev parent reply other threads:[~2003-05-23 14:10 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-19 23:15 northern snowfall
2003-05-19 22:24 ` Russ Cox
2003-05-19 22:14 ` Charles Forsyth
2003-05-19 23:29 ` northern snowfall
2003-05-19 22:38 ` Russ Cox
2003-05-19 23:45 ` northern snowfall
2003-05-21 17:27 ` rog
2003-05-21 17:26 ` Russ Cox
2003-05-21 18:28 ` northern snowfall
2003-05-21 17:33 ` Russ Cox
2003-05-21 18:50 ` rog
2003-05-22 1:09 ` okamoto
2003-05-22 9:46 ` C H Forsyth
2003-05-23 1:07 ` okamoto
2003-05-23 14:10 ` Russ Cox [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=5b2174369b9c532c6b867044a5ae75b5@plan9.bell-labs.com \
--to=rsc@plan9.bell-labs.com \
--cc=9fans@cse.psu.edu \
/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).