From: "Russ Cox" <rsc@swtch.com>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu>
Subject: Re: [9fans] thread cleanup
Date: Wed, 6 Sep 2006 16:20:44 -0400 [thread overview]
Message-ID: <ee9e417a0609061320k205a5477ub59acf6c50906e08@mail.gmail.com> (raw)
In-Reply-To: <9d16c55abf73992d77356892ea9e3c27@9netics.com>
threadexitsall should take it down (and everything else).
don't use threadkill or postnote. instead send the thread
something on the channel it's waiting on (like a nil)
indicating that it should exit cleanly.
i'm very surprised that threadexitsall doesn't work.
if you can create a simple test program demonstrating
a hang after threadexitsall, i'd like to see it.
russ
On 9/6/06, Skip Tavakkolian <9nut@9netics.com> wrote:
> in an fs i wrote that's using thread library, the parent can't kill the child.
> the child was started by proccreate and is in Rendez state; the thread
> in the child is running a function that waits on a channel (recvp);
>
> in fs.end(), i've tried threadexitsall, threadkill, and postnote --
> PNPROC and PNGROUP -- but nothing worked. what am i missing?
>
> child process state:
> cpu% acid 698004
> /proc/698004/text:386 plan 9 executable
>
> /sys/lib/acid/port
> /sys/lib/acid/386
> acid: stk()
> rendezvous()+0x7 /sys/src/libc/9syscall/rendezvous.s:5
> runthread(p=0x29a48)+0x83 /sys/src/libthread/sched.c:144
> _sched()+0x90 /sys/src/libthread/sched.c:113
> _schedinit(arg=0x29a48)+0x1a4 /sys/src/libthread/sched.c:77
> main(argc=0x4,argv=0x7fffef9c)+0x38 /sys/src/libthread/main.c:34
> _main+0x31 /sys/src/libc/386/main9.s:16
> acid:
>
>
next prev parent reply other threads:[~2006-09-06 20:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-06 18:34 Skip Tavakkolian
2006-09-06 20:20 ` Russ Cox [this message]
2006-09-06 22:11 ` Skip Tavakkolian
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=ee9e417a0609061320k205a5477ub59acf6c50906e08@mail.gmail.com \
--to=rsc@swtch.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).