Netgate Discussion Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search
    • Register
    • Login

    Is anyone using dtrace in a pfSense dev build?

    Development
    1
    2
    1.9k
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • M
      markky
      last edited by

      Hi,

      Has anyone successfully got dtrace working in a pfsense/freesbie build environment?

      Looking around builder_common.sh, it looks like including dtrace support in a kernel is a simple as setting an environment variable.
      i.e. something like
        export WITH_DTRACE="YES"

      Unfortunately it doesn't work, at least in my experience.

      Generally with FreeBSD, there's a couple of things you need to get DTRACE working, some has to do with kernel config, some to do with compile options, but it's all pretty straightforward.

      What's very odd with the pfSense build environment is that something seems to be redefining CTFCONVERT as null.

      At the top, i.e.
       /usr/pfSensesrc/src/Makefile.inc1,
      CTFCONVERT is correct, however by the time you get down to a module Makefile, such as

      /usr/pfSensesrc/src/sys/modules/i2c/controllers/amdsmb

      CTFFLAGS is still set, but CTFCONVERT is now an empty string, which means that the command run after compilation is "-L VERSION …" instead of "ctfconvert -L VERSION ..."

      If I'm missing something obvious, please point it out.

      Thanks,

      • Mark
      1 Reply Last reply Reply Quote 0
      • M
        markky
        last edited by

        @markky:

        Hi,

        Has anyone successfully got dtrace working in a pfsense/freesbie build environment?

        Looking around builder_common.sh, it looks like including dtrace support in a kernel is a simple as setting an environment variable.
        i.e. something like
          export WITH_DTRACE="YES"

        Unfortunately it doesn't work, at least in my experience.

        Generally with FreeBSD, there's a couple of things you need to get DTRACE working, some has to do with kernel config, some to do with compile options, but it's all pretty straightforward.

        What's very odd with the pfSense build environment is that something seems to be redefining CTFCONVERT as null.

        At the top, i.e.
         /usr/pfSensesrc/src/Makefile.inc1,
        CTFCONVERT is correct, however by the time you get down to a module Makefile, such as

        /usr/pfSensesrc/src/sys/modules/i2c/controllers/amdsmb

        CTFFLAGS is still set, but CTFCONVERT is now an empty string, which means that the command run after compilation is "-L VERSION …" instead of "ctfconvert -L VERSION ..."

        If I'm missing something obvious, please point it out.

        Thanks,

        • Mark

        Well, I think I've worked out what was going wrong with the Makefiles, and it definitely wasn't obvious, imo.
        I'll write up why the build was failing in the next couple of days.  Still verifying the final bits.

        Cheers,

        • Mark
        1 Reply Last reply Reply Quote 0
        • First post
          Last post
        Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.