Date: Sun, 15 Apr 2012 20:57:32 +0000 From: Alexander Best <arundel@freebsd.org> To: Alexander Leidinger <Alexander@Leidinger.net> Cc: freebsd-emulation@freebsd.org Subject: Re: [PATCH] pipe2 for Linuxulator Message-ID: <20120415205732.GA65853@freebsd.org> In-Reply-To: <20120415211656.000053b9@unknown> References: <20120415134444.000005cc@unknown> <20120415115112.GA83717@freebsd.org> <20120415143441.00000948@unknown> <20120415130306.GA95208@freebsd.org> <20120415163059.0000715d@unknown> <20120415144155.GA15993@freebsd.org> <20120415181613.GA52958@freebsd.org> <20120415205302.00005855@unknown> <20120415190408.GA61246@freebsd.org> <20120415211656.000053b9@unknown>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun Apr 15 12, Alexander Leidinger wrote: > On Sun, 15 Apr 2012 19:04:08 +0000 Alexander Best <arundel@freebsd.org> > wrote: > > > On Sun Apr 15 12, Alexander Leidinger wrote: > > > On Sun, 15 Apr 2012 18:16:13 +0000 Alexander Best > > > <arundel@freebsd.org> wrote: > > > > > also...even after installing a fresh kernel and world with dtrace > > > > enabled, the "check_error.d" and "trace_futexes.d" fail and > > > > sometimes even render the flash instance unusable. > > > > > > I assume with unusable you mean not fast enough. Well... buy a > > > faster CPU. No, just kidding. Depending on what a D script does and > > > how many probes are enabled in the D script, it is not unexpected > > > that the system slows down. As told above, the scripts show what is > > > possible. For real debugging you may want to use stripped down > > > versions. > > > > no actually. what i meant by "unusable" is that the d-scripts > > themself crash the flash instances. > > Uhm... this is unexpected. DTrace disables destructive actions by > default, and I do not activate them. Maybe some timing-sensitive code > in the flash-player which does not handle the case that some parts can > take longer than expected? I assume there is not bug in DTrace itself. > There could be a bug in my patch, but I would assume it is not a > heisen-bug as described here (the probes are handled by > DTrace-macros, just the variables which are provided to D scripts > are different from other probes). this sounds reasonable. after exiting the dtrace script the crashed flash instance partially returns to normal behaviour. so indeed it seems that dtrace is having only an impact on flash's timing-code. none of the linux processes actually crashes (that is is being terminated) in this scenario. ps alx shows that all processes still exist. i'll play a bit more with the dtrace scripts and see if i can remove more stuff that isn't important for futex related matters. good night. alex > > Bye, > Alexander. > > -- > http://www.Leidinger.net Alexander @ Leidinger.net: PGP ID = B0063FE7 > http://www.FreeBSD.org netchild @ FreeBSD.org : PGP ID = 72077137
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20120415205732.GA65853>