Hi,
I am seeing this panic when trying to use DTrace on r299073. I
cannot rule out that it's my (experimental) environment; just wanted
to check if it might have been a known breakage before digging into it.
# dtrace -n 'dtrace:::BEGIN { printf("Hello FreeBSD!\n"); }'
dtrace -n
of a small inline function was called and I
ended up adding SDT probes and passing __func__ and __LINE__ into
them so figure the culprits out.
Has anyone else observed something like this lately?
/bz
--
Bjoern A. Zeeb r15:7
almost
as if headers weren't visible anymore or something?
Thanks,
/bz
--
Bjoern A. Zeeb r15:7
On Fri, 11 Feb 2022, Mark Johnston wrote:
On Fri, Feb 11, 2022 at 09:23:47AM -0500, Mark Johnston wrote:
On Fri, Feb 11, 2022 at 02:10:30PM +, Bjoern A. Zeeb wrote:
Hi,
one of the drawbacks of Dtrace (and other tracing frameworks out there
on various OSes) is that they do need a list
d_load, lf);
*result = lf;
return (0);
}
--
Bjoern A. Zeeb r15:7
On Mon, 14 Feb 2022, Mark Johnston wrote:
Hi,
sorry I had lost track ..
On Sat, Feb 12, 2022 at 12:16:45AM +, Bjoern A. Zeeb wrote:
On Fri, 11 Feb 2022, Mark Johnston wrote:
It appears to be sufficient to simply move the kld_load hook to before
module registration, patch below
On Thu, 24 Mar 2022, Bjoern A. Zeeb wrote:
Hi,
On Mon, 14 Feb 2022, Mark Johnston wrote:
Hi,
sorry I had lost track ..
On Sat, Feb 12, 2022 at 12:16:45AM +, Bjoern A. Zeeb wrote:
On Fri, 11 Feb 2022, Mark Johnston wrote:
It appears to be sufficient to simply move the kld_load hook
Hi,
compiling with gcc I see a lot of:
ERROR: ctfconvert: rc = 1 Unsupported version [_dwarf_info_load(229)]
I wonder "Unsupported version" of what? and can we improve it?
/bz
--
Bjoern A. Zeeb r15:7
