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
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
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,
Actually the error only appears on arm64 for me. I moved the script
to amd64 and it works as I thought.
Martin
Martin Cracauer wrote on Sun, Jan 22, 2023 at 08:54:31PM -0500:
> I want to capture the (userland) stack trace on top of the write(2)
> system call. I seem to have some difficulty