Date: Tue, 24 Jan 2023 11:15:46 -0500 From: Mark Johnston <markj@freebsd.org> To: Martin Cracauer <cracauer@cons.org> Cc: freebsd-dtrace@freebsd.org Subject: Re: DTrace - capturing two userspace strack frames on top of system call Message-ID: <Y9AEMq1Gev5sWinH@nuc> In-Reply-To: <Y88B/bFsjbyjh/AK@cons.org> References: <Y83o15sbizWURbsr@cons.org> <Y835UomAxqh3EwRY@cons.org> <Y867PBRdCiuyE%2BOX@nuc> <Y88B/bFsjbyjh/AK@cons.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, Jan 23, 2023 at 04:54:05PM -0500, Martin Cracauer wrote:
> Mark Johnston wrote on Mon, Jan 23, 2023 at 11:52:12AM -0500:
> > On Sun, Jan 22, 2023 at 10:04:50PM -0500, Martin Cracauer wrote:
> > > Actually the error only appears on arm64 for me. I moved the script
> > > to amd64 and it works as I thought.
> >
> > Support for userspace tracing on arm64 is definitely less mature than on
> > amd64, so this isn't too surprising, unfortunately.
> >
> > Is the problem reproducible with a trivial program compiled with
> > -fno-omit-frame-pointer?
>
> Yes:
> $ gcc -O2 -fno-omit-frame-pointer -Wall -Werror -o crasparse crasparse.c
> # dtrace -n 'syscall::write*:entry /arg1/ { @traces[ustack()] = count(); }' -c ./crasparse
> dtrace: error on enabled probe ID 1 (ID 57136: syscall:freebsd:writev:entry): invalid address (0x0) in action #2
> [...]
>
> Should I make a bugzilla entry out of this?
Yes please, that would be helpful.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Y9AEMq1Gev5sWinH>