Date: Mon, 11 Oct 1999 12:46:29 -0600 (MDT) From: Chad David <davidc@acns.ab.ca> To: Chris Costello <chris@calldei.com> Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: aio_read kills machine Message-ID: <Pine.BSF.4.10.9910111239540.369-100000@colnta.acns.ab.ca> In-Reply-To: <19991010204252.D15135@holly.calldei.com>
next in thread | previous in thread | raw e-mail | index | archive | help
I have submitted a PR. Upon closer inspection I found that it is not (directly) the call to aio_read() that kills the machine, but instead a call to sched_yield() after a call to pthread_cond_wait() with a NULL in the mutex field. Even a print statement before the call to sched_yield() prevents the kill. Some replys indicated that I should use -current for aio_*. Would this be true also for any serious threading? Is -current ready for a semi-production environment? The source for this code is available from http://www.guild.ab.ca/killer.tar.gz if anyone would like to take a look. The crash has been truncating main.c, so you may want to copy it before running the program. Thanks. Chad On Sun, 10 Oct 1999, Chris Costello wrote: > On Wed, Jan 01, 1997, Chad David wrote: > > I am certain that my program is not correct > > (besides the obvious consiquence of running > > it :) ), but I would also like to determine > > why it kills the machine. I was not root > > either time I ran the code. > > Then FreeBSD does have a problem. Please file a PR using the > ``send-pr'' command or http://www.freebsd.org/send-pr.html and > supply the source to your program and whatever other information > you think will help us in figuring out the problem. > > -- > |Chris Costello <chris@calldei.com> > |Field tested: Manufacturing doesn't have a test system. > `------------------------------------------------------- > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.10.9910111239540.369-100000>