NetBSD-Bugs archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]

Re: bin/58692: opensnoop fails -- dtrace fails printing arg0



The following reply was made to PR bin/58692; it has been noted by GNATS.

From: RVP <rvp%SDF.ORG@localhost>
To: gnats-bugs%netbsd.org@localhost
Cc: 
Subject: Re: bin/58692: opensnoop fails -- dtrace fails printing arg0
Date: Tue, 24 Sep 2024 23:59:07 +0000 (UTC)

 On Tue, 24 Sep 2024, nmingotti%gmail.com@localhost wrote:
 
 >> Description:
 >
 > . /usr/sbin/opensnoop fails giving (as soon as a file is open) a lot of errors
 >
 > . The problem appears to be related to dtrace printing arg0
 >
 >> How-To-Repeat:
 >
 > $> doas /usr/sbin/opensnoop
 > ---------- output --------------
 > dtrace: error on enabled probe ID 3 (ID 371: syscall::open:return): invalid address (0x7f7fffbd9ee0) in action #10 at DIF offset 12
 > : No such file or directory
 > dtrace: error on enabled probe ID 3 (ID 371: syscall::open:return): invalid address (0x7992e579394b) in action #10 at DIF offset 12
 > : No such file or directory
 > ....
 > --------------------------------
 >
 > . I used a bit DTrace  in the past, the problem appears to be related to the print of "arg0". Indeed:
 > . this works:
 > $> doas /usr/sbin/dtrace -n 'syscall::open:entry { printf(". open file - %s", execname); } '
 >
 > . but this fails
 > doas /usr/sbin/dtrace -n 'syscall::open:entry { printf("%s %s", execname, copyinstr(arg0)); } '
 > ---- output ----------------------
 > dtrace: error on enabled probe ID 1 (ID 370: syscall::open:entry): invalid address (0x7f7ffffbaeb0) in action #2 at DIF offset 12
 > : No such file or directory
 > dtrace: error on enabled probe ID 1 (ID 370: syscall::open:entry): invalid address (0x7f7ffffba5e0) in action #2 at DIF offset 12
 > : No such file or directory
 > ...
 > -----------------------------------
 >
 
 This was fixed in -HEAD last year, and I had thought it had been pulled up
 to 10.0:
 
 https://github.com/NetBSD/src/commit/feabd72f0cb81bd667c516878fdcc23c4f5dd736
 
 but, evidently not. Please request it.
 
 -RVP
 


Home | Main Index | Thread Index | Old Index