Date: Thu, 5 Sep 2002 15:07:23 -0600 From: John E Hein <jhein@timing.com> To: Duncan Barclay <dmlb@dmlb.org> Cc: emulation@FreeBSD.ORG Subject: fix for Linux matlab exit behaviour - problem with linux_clone(2 Message-ID: <15735.51083.489854.267762@brain.timing.com> In-Reply-To: <XFMail.20020905215556.dmlb@computer.my.domain> References: <XFMail.20020905194033.dmlb@computer.my.domain> <XFMail.20020905215556.dmlb@computer.my.domain>
next in thread | previous in thread | raw e-mail | index | archive | help
Duncan Barclay wrote at 21:55 +0100 on Sep 5: > Please review the following PR for a hack to let matlab exit. > > http://www.freebsd.org/cgi/query-pr.cgi?pr=42457 > > The code in PR is deliberatly not a patch because it is not the right way > to cleanly fix the problem. > > The problem is that we do not fully emulate all of linux_clone(2) behaviour, > in particular, linux_clone(2) allows a thread to not send a signal to > its parent on exit. /sys/kern_exit.c does not allow this and will > send a specified signal or SIGCHLD. Matlab has a SIGCHLD handler that > does not reap threads. If the SIGCHLD is not sent, matlab reaps its last > thread and exits cleanly. Interesting... so why then does the /dev/ptmx -> /dev/null hack allow us to exit matlab? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-emulation" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?15735.51083.489854.267762>