Re: kern/50790 (Kernel panic induced by dtrace.)

[christos%zoulas.com@localhost (Christos Zoulas)]

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

From: christos%zoulas.com@localhost (Christos Zoulas)
To: gnats-bugs%NetBSD.org@localhost, kern-bug-people%netbsd.org@localhost, 
	gnats-admin%netbsd.org@localhost, netbsd-bugs%netbsd.org@localhost, coypu%sdf.org@localhost
Cc: 
Subject: Re: kern/50790 (Kernel panic induced by dtrace.)
Date: Thu, 26 May 2016 08:59:29 -0400

 On May 26,  9:55am, coypu%SDF.ORG@localhost (coypu%SDF.ORG@localhost) wrote:
 -- Subject: Re: kern/50790 (Kernel panic induced by dtrace.)
 
 | The following reply was made to PR kern/50790; it has been noted by GNATS.
 | 
 | From: coypu%SDF.ORG@localhost
 | To: gnats-bugs%NetBSD.org@localhost
 | Cc: 
 | Subject: Re: kern/50790 (Kernel panic induced by dtrace.)
 | Date: Thu, 26 May 2016 09:52:56 +0000
 | 
 |  Hi, I can't no longer produce a panic (thus the problem is fixed)
 |  
 |  # dtrace -n syscall:::entry'/execname == "bash"/{@[ustack()] = count()}'
 |  dtrace: invalid probe specifier syscall:::entry/execname == "bash"/{@[ustack()] = count()}: "/usr/lib/dtrace/psinfo.d", line 46: syntax error near "u_int"
 |  
 |  However, I don't know if it works.
 
 This just means that your kernel is missing ctf information to find u_int,
 so you are not making it far enough to panic.
 
 christos