dtrace(1) error in the kernel built by build.sh kernel=GENERIC

[Kengo NAKAHARA <k-nakahara%iij.ad.jp@localhost>]

Hi,

When I use the kernel built by "build.sh kernel=GENERIC" (the source is
updated at March 31), I find dtrace(1) error which prints the following
message.
========== NG result ==========
# dtrace -n 'proc::: {}'
dtrace: invalid probe specifier proc::: {}: "/usr/lib/dtrace/psinfo.d", line 46: failed to copy type of 'pr_arglen': Type information is in parent and unavailable
========== NG result ==========

In contrast, when I apply the following patch, the same dtrace(1) command
succeed.
========== patch ==========
--- a/sys/arch/amd64/conf/GENERIC
+++ b/sys/arch/amd64/conf/GENERIC
@@ -103,7 +103,7 @@ options     DDB             # in-kernel debugger
 options        DDB_HISTORY_SIZE=512    # enable history editing in DDB
 #options       KGDB            # remote debugger
 #options       KGDB_DEVNAME="\"com\"",KGDB_DEVADDR=0x3f8,KGDB_DEVRATE=9600
-makeoptions    DEBUG="-g"      # compile full symbol table for CTF
+#makeoptions   DEBUG="-g"      # compile full symbol table for CTF
 #options       SYSCALL_STATS   # per syscall counts
 #options       SYSCALL_TIMES   # per syscall times
 #options       SYSCALL_TIMES_HASCOUNTER        # use 'broken' rdtsc (soekris)
========== patch ==========

========== ok result ==========
netbsd-rangeley# dtrace -n 'proc::: {}'
dtrace: description 'proc::: ' matched 12 probes
# do some command such as ls(1)
  7    208                      :lwp-create 
  7    205                          :create 
  7    207                       :lwp-start 
  7    203                            :exec 
  7    202                    :exec-success 
  7    204                            :exit 
  7    210                  :signal-discard 
========== ok result ==========

# BTW, when I use the kernel built by "build.sh release", the same
# dtrace(1) command succeed, because it does "nbconfig -U DEBUG".

I am not sure the above patch might be appropriate or not, but I have
no idea to fix this problem by other way.

Does anyone has any comments about this problem?


Thanks,

-- 
//////////////////////////////////////////////////////////////////////
Internet Initiative Japan Inc.

Device Engineering Section,
IoT Platform Development Department,
Network Division,
Technology Unit

Kengo NAKAHARA <k-nakahara%iij.ad.jp@localhost>