Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 29 Nov 2021 10:03:33 +0100
From:      Mateusz Piotrowski <0mp@FreeBSD.org>
To:        "Bjoern A. Zeeb" <bzeeb-lists@lists.zabbadoz.net>, dtrace@freebsd.org
Subject:   Re: something broke Dtrace scripts?
Message-ID:  <5cad7bf3-c865-0c0e-cdbb-21479c7cab23@FreeBSD.org>
In-Reply-To: <alpine.BSF.2.00.2111181919390.68830@ai.fobar.qr>
References:  <alpine.BSF.2.00.2111181919390.68830@ai.fobar.qr>

next in thread | previous in thread | raw e-mail | index | archive | help
On 18/11/2021 20:25, Bjoern A. Zeeb wrote:
> Hi,
>
> I updated my VM to a recent main and dtrace -l still works fine but
> running any script stopped working.
>
> A very easy way to reproduce the initial problem is simply:
>
> root@bhyve:/tmp # touch z.d
> root@bhyve:/tmp # dtrace -s z.d
> dtrace: failed to compile script z.d: "/usr/lib/dtrace/mbuf.d", line 1: failed to copy type of 
> 'm_data': Type information is in parent and unavailable
>
> Can someone de-tangle that message and how to fix it?
>
> I know if I change the caddr_t to uintptr_t in the mbuf.d it'll start
> complaining about "cannot find type: struct mbuf*: ..."  It is almost
> as if headers weren't visible anymore or something?
What version version are you running? On FreeBSD 14.0-CURRENT main-n250590-2de49deeca0b DTrace works 
fine.



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?5cad7bf3-c865-0c0e-cdbb-21479c7cab23>