Re: wrong value from DTRACE (uint32 for int64)

2019-12-02 Thread Peter
On Mon, 02 Dec 2019 21:58:36 +0100, Mark Johnston wrote: The DTRACE_PROBE* macros cast their parameters to uintptr_t, which will be 32 bits wide on i386. You might be able to work around the problem by casting arg0 to uint32_t in the script. Thanks for the info - good that it has a logical e

Re: wrong value from DTRACE (uint32 for int64)

2019-12-02 Thread Mark Johnston
On Mon, Dec 02, 2019 at 08:44:59PM +0100, Peter wrote: > Hi @all, > > I felt the need to look into my ZFS ARC, but DTRACE provided misleading > (i.e., wrong) output (on i386, 11.3-RELEASE): > > # dtrace -Sn 'arc-available_memory { printf("%x %x", arg0, arg1); }' > DIFO 0x286450a0 returns D type

wrong value from DTRACE (uint32 for int64)

2019-12-02 Thread Peter
Hi @all, I felt the need to look into my ZFS ARC, but DTRACE provided misleading (i.e., wrong) output (on i386, 11.3-RELEASE): # dtrace -Sn 'arc-available_memory { printf("%x %x", arg0, arg1); }' DIFO 0x286450a0 returns D type (integer) (size 8) OFF OPCODE INSTRUCTION 00: 29010601ldg