Date: Tue, 5 Nov 2019 22:20:18 +0200 From: Andriy Gapon <avg@FreeBSD.org> To: "Bjoern A. Zeeb" <bzeeb-lists@lists.zabbadoz.net>, freebsd-dtrace@freebsd.org Subject: Re: dtrace script matching lot of probes simply resets on i386 Message-ID: <d8b0ebd4-ba6d-38eb-fadd-d8a007205191@FreeBSD.org> In-Reply-To: <71FB27F2-31DD-4646-BAA8-69E686D811DE@lists.zabbadoz.net> References: <71FB27F2-31DD-4646-BAA8-69E686D811DE@lists.zabbadoz.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On 05/11/2019 13:23, Bjoern A. Zeeb wrote:
> Hi,
>
> I had an i386 kernel (amd64 machine) simply going to POST. After a lot of “doh”
> I realised that it was a dtrace script which was matching a lot of probes
> running as part of some automated stuff.
>
> The problematic part from the middle of that script was a section which I can
> reduce to
>
> fbt:kernel::entry # or simply :::
> /self->foo == 1/
> {
>
> printf(“Hello\n”);
> }
>
> Anyone wants to investigate this or should I open a PR?
My first suspicion is that something in dtrace internals is not excluded and
gets matched by the probe resulting in a recursion.
But I am not sure how to approach finding that something.
Looking through dtrace -l -P fbt for something that stands out is not going to
be easy.
--
Andriy Gapon
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?d8b0ebd4-ba6d-38eb-fadd-d8a007205191>