Problem reports for dtr...@freebsd.org that need special attention
To view an individual PR, use: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id). The following is a listing of current problems submitted by FreeBSD users, which need special attention. These represent problem reports covering all versions including experimental development code and obsolete releases. Status |Bug Id | Description +---+--- Open|267619 | dtrace: Compiler produces bogus error message: in 1 problems total for which you should take action.
Problem reports for dtr...@freebsd.org that need special attention
To view an individual PR, use: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id). The following is a listing of current problems submitted by FreeBSD users, which need special attention. These represent problem reports covering all versions including experimental development code and obsolete releases. Status |Bug Id | Description +---+--- Open|267619 | dtrace: Compiler produces bogus error message: in 1 problems total for which you should take action.
Problem reports for dtr...@freebsd.org that need special attention
To view an individual PR, use: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id). The following is a listing of current problems submitted by FreeBSD users, which need special attention. These represent problem reports covering all versions including experimental development code and obsolete releases. Status |Bug Id | Description +---+--- Open|267619 | dtrace: Compiler produces bogus error message: in 1 problems total for which you should take action.
Problem reports for dtr...@freebsd.org that need special attention
To view an individual PR, use: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id). The following is a listing of current problems submitted by FreeBSD users, which need special attention. These represent problem reports covering all versions including experimental development code and obsolete releases. Status |Bug Id | Description +---+--- Open|267619 | dtrace: Compiler produces bogus error message: in 1 problems total for which you should take action.
Problem reports for dtr...@freebsd.org that need special attention
To view an individual PR, use: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id). The following is a listing of current problems submitted by FreeBSD users, which need special attention. These represent problem reports covering all versions including experimental development code and obsolete releases. Status |Bug Id | Description +---+--- Open|267619 | dtrace: Compiler produces bogus error message: in 1 problems total for which you should take action.
Problem reports for dtr...@freebsd.org that need special attention
To view an individual PR, use: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id). The following is a listing of current problems submitted by FreeBSD users, which need special attention. These represent problem reports covering all versions including experimental development code and obsolete releases. Status |Bug Id | Description +---+--- Open|267619 | dtrace: Compiler produces bogus error message: in 1 problems total for which you should take action.
Problem reports for dtr...@freebsd.org that need special attention
To view an individual PR, use: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id). The following is a listing of current problems submitted by FreeBSD users, which need special attention. These represent problem reports covering all versions including experimental development code and obsolete releases. Status |Bug Id | Description +---+--- Open|267619 | dtrace: Compiler produces bogus error message: in 1 problems total for which you should take action.
Problem reports for dtr...@freebsd.org that need special attention
To view an individual PR, use: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id). The following is a listing of current problems submitted by FreeBSD users, which need special attention. These represent problem reports covering all versions including experimental development code and obsolete releases. Status |Bug Id | Description +---+--- Open|267619 | dtrace: Compiler produces bogus error message: in 1 problems total for which you should take action.
Problem reports for dtr...@freebsd.org that need special attention
To view an individual PR, use: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id). The following is a listing of current problems submitted by FreeBSD users, which need special attention. These represent problem reports covering all versions including experimental development code and obsolete releases. Status |Bug Id | Description +---+--- Open|267619 | dtrace: Compiler produces bogus error message: in 1 problems total for which you should take action.
Problem reports for dtr...@freebsd.org that need special attention
To view an individual PR, use: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id). The following is a listing of current problems submitted by FreeBSD users, which need special attention. These represent problem reports covering all versions including experimental development code and obsolete releases. Status |Bug Id | Description +---+--- Open|267619 | dtrace: Compiler produces bogus error message: in 1 problems total for which you should take action.
Problem reports for dtr...@freebsd.org that need special attention
To view an individual PR, use: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id). The following is a listing of current problems submitted by FreeBSD users, which need special attention. These represent problem reports covering all versions including experimental development code and obsolete releases. Status |Bug Id | Description +---+--- Open|267619 | dtrace: Compiler produces bogus error message: in 1 problems total for which you should take action.
Problem reports for dtr...@freebsd.org that need special attention
To view an individual PR, use: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id). The following is a listing of current problems submitted by FreeBSD users, which need special attention. These represent problem reports covering all versions including experimental development code and obsolete releases. Status |Bug Id | Description +---+--- Open|267619 | dtrace: Compiler produces bogus error message: in 1 problems total for which you should take action.
Problem reports for dtr...@freebsd.org that need special attention
To view an individual PR, use: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id). The following is a listing of current problems submitted by FreeBSD users, which need special attention. These represent problem reports covering all versions including experimental development code and obsolete releases. Status |Bug Id | Description +---+--- Open|267619 | dtrace: Compiler produces bogus error message: in 1 problems total for which you should take action.
[Bug 232675] dtrace: "failed to compile script" when more than 2^15 distinct types are in CTF info
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=232675 Mathieu Arnold changed: What|Removed |Added CC||ohartm...@walstatt.org --- Comment #54 from Mathieu Arnold --- *** Bug 265689 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are on the CC list for the bug.
Problem reports for dtr...@freebsd.org that need special attention
To view an individual PR, use: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id). The following is a listing of current problems submitted by FreeBSD users, which need special attention. These represent problem reports covering all versions including experimental development code and obsolete releases. Status |Bug Id | Description +---+--- Open|267619 | dtrace: Compiler produces bogus error message: in 1 problems total for which you should take action.
Problem reports for dtr...@freebsd.org that need special attention
To view an individual PR, use: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id). The following is a listing of current problems submitted by FreeBSD users, which need special attention. These represent problem reports covering all versions including experimental development code and obsolete releases. Status |Bug Id | Description +---+--- Open|267619 | dtrace: Compiler produces bogus error message: in 1 problems total for which you should take action.
Problem reports for dtr...@freebsd.org that need special attention
To view an individual PR, use: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id). The following is a listing of current problems submitted by FreeBSD users, which need special attention. These represent problem reports covering all versions including experimental development code and obsolete releases. Status |Bug Id | Description +---+--- Open|267619 | dtrace: Compiler produces bogus error message: in 1 problems total for which you should take action.
Problem reports for dtr...@freebsd.org that need special attention
To view an individual PR, use: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id). The following is a listing of current problems submitted by FreeBSD users, which need special attention. These represent problem reports covering all versions including experimental development code and obsolete releases. Status |Bug Id | Description +---+--- Open|267619 | dtrace: Compiler produces bogus error message: in 1 problems total for which you should take action.
Problem reports for dtr...@freebsd.org that need special attention
To view an individual PR, use: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id). The following is a listing of current problems submitted by FreeBSD users, which need special attention. These represent problem reports covering all versions including experimental development code and obsolete releases. Status |Bug Id | Description +---+--- Open|267619 | dtrace: Compiler produces bogus error message: in 1 problems total for which you should take action.
Problem reports for dtr...@freebsd.org that need special attention
To view an individual PR, use: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id). The following is a listing of current problems submitted by FreeBSD users, which need special attention. These represent problem reports covering all versions including experimental development code and obsolete releases. Status |Bug Id | Description +---+--- Open|267619 | dtrace: Compiler produces bogus error message: in 1 problems total for which you should take action.
Problem reports for dtr...@freebsd.org that need special attention
To view an individual PR, use: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id). The following is a listing of current problems submitted by FreeBSD users, which need special attention. These represent problem reports covering all versions including experimental development code and obsolete releases. Status |Bug Id | Description +---+--- Open|267619 | dtrace: Compiler produces bogus error message: in 1 problems total for which you should take action.
Problem reports for dtr...@freebsd.org that need special attention
To view an individual PR, use: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id). The following is a listing of current problems submitted by FreeBSD users, which need special attention. These represent problem reports covering all versions including experimental development code and obsolete releases. Status |Bug Id | Description +---+--- Open|267619 | dtrace: Compiler produces bogus error message: in 1 problems total for which you should take action.
Problem reports for dtr...@freebsd.org that need special attention
To view an individual PR, use: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id). The following is a listing of current problems submitted by FreeBSD users, which need special attention. These represent problem reports covering all versions including experimental development code and obsolete releases. Status |Bug Id | Description +---+--- Open|267619 | dtrace: Compiler produces bogus error message: in 1 problems total for which you should take action.
Problem reports for dtr...@freebsd.org that need special attention
To view an individual PR, use: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id). The following is a listing of current problems submitted by FreeBSD users, which need special attention. These represent problem reports covering all versions including experimental development code and obsolete releases. Status |Bug Id | Description +---+--- Open|267619 | dtrace: Compiler produces bogus error message: in 1 problems total for which you should take action.
Problem reports for dtr...@freebsd.org that need special attention
To view an individual PR, use: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id). The following is a listing of current problems submitted by FreeBSD users, which need special attention. These represent problem reports covering all versions including experimental development code and obsolete releases. Status |Bug Id | Description +---+--- Open|267619 | dtrace: Compiler produces bogus error message: in 1 problems total for which you should take action.
Problem reports for dtr...@freebsd.org that need special attention
To view an individual PR, use: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id). The following is a listing of current problems submitted by FreeBSD users, which need special attention. These represent problem reports covering all versions including experimental development code and obsolete releases. Status |Bug Id | Description +---+--- Open|267619 | dtrace: Compiler produces bogus error message: in 1 problems total for which you should take action.
Problem reports for dtr...@freebsd.org that need special attention
To view an individual PR, use: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id). The following is a listing of current problems submitted by FreeBSD users, which need special attention. These represent problem reports covering all versions including experimental development code and obsolete releases. Status |Bug Id | Description +---+--- Open|267619 | dtrace: Compiler produces bogus error message: in 1 problems total for which you should take action.
Problem reports for dtr...@freebsd.org that need special attention
To view an individual PR, use: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id). The following is a listing of current problems submitted by FreeBSD users, which need special attention. These represent problem reports covering all versions including experimental development code and obsolete releases. Status |Bug Id | Description +---+--- Open|267619 | dtrace: Compiler produces bogus error message: in 1 problems total for which you should take action.
Problem reports for dtr...@freebsd.org that need special attention
To view an individual PR, use: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id). The following is a listing of current problems submitted by FreeBSD users, which need special attention. These represent problem reports covering all versions including experimental development code and obsolete releases. Status |Bug Id | Description +---+--- Open|267619 | dtrace: Compiler produces bogus error message: in 1 problems total for which you should take action.
Problem reports for dtr...@freebsd.org that need special attention
To view an individual PR, use: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id). The following is a listing of current problems submitted by FreeBSD users, which need special attention. These represent problem reports covering all versions including experimental development code and obsolete releases. Status |Bug Id | Description +---+--- Open|267619 | dtrace: Compiler produces bogus error message: in 1 problems total for which you should take action.
Problem reports for dtr...@freebsd.org that need special attention
To view an individual PR, use: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id). The following is a listing of current problems submitted by FreeBSD users, which need special attention. These represent problem reports covering all versions including experimental development code and obsolete releases. Status |Bug Id | Description +---+--- Open|267619 | dtrace: Compiler produces bogus error message: in 1 problems total for which you should take action.
Problem reports for dtr...@freebsd.org that need special attention
To view an individual PR, use: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id). The following is a listing of current problems submitted by FreeBSD users, which need special attention. These represent problem reports covering all versions including experimental development code and obsolete releases. Status |Bug Id | Description +---+--- Open|267619 | dtrace: Compiler produces bogus error message: in 1 problems total for which you should take action.
Problem reports for dtr...@freebsd.org that need special attention
To view an individual PR, use: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id). The following is a listing of current problems submitted by FreeBSD users, which need special attention. These represent problem reports covering all versions including experimental development code and obsolete releases. Status |Bug Id | Description +---+--- Open|267619 | dtrace: Compiler produces bogus error message: in 1 problems total for which you should take action.
Problem reports for dtr...@freebsd.org that need special attention
To view an individual PR, use: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id). The following is a listing of current problems submitted by FreeBSD users, which need special attention. These represent problem reports covering all versions including experimental development code and obsolete releases. Status |Bug Id | Description +---+--- Open|267619 | dtrace: Compiler produces bogus error message: in 1 problems total for which you should take action.
[Bug 232675] dtrace: "failed to compile script" when more than 2^15 distinct types are in CTF info
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=232675 Cory Albrecht changed: What|Removed |Added CC||free...@cory.albrecht.name --- Comment #53 from Cory Albrecht --- I am also hitting the "in_addr_t" bug with ipfw.d building with poudriere in a 13.1-RELEASE-p9 jail on TrueNAS -- You are receiving this mail because: You are on the CC list for the bug.
Problem reports for dtr...@freebsd.org that need special attention
To view an individual PR, use: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id). The following is a listing of current problems submitted by FreeBSD users, which need special attention. These represent problem reports covering all versions including experimental development code and obsolete releases. Status |Bug Id | Description +---+--- Open|267619 | dtrace: Compiler produces bogus error message: in 1 problems total for which you should take action.
[Bug 232675] dtrace: "failed to compile script" when more than 2^15 distinct types are in CTF info
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=232675 Alex Rosenberg changed: What|Removed |Added CC||al...@leftfield.org --- Comment #52 from Alex Rosenberg --- Also hitting this with my poudriere jail building perl5-5.34 on TrueNAS-13.0-U5.3. total number of data objects= 37964 Reported as https://ixsystems.atlassian.net/browse/NAS-123532 -- You are receiving this mail because: You are on the CC list for the bug.
[Bug 269906] dtrace requires empty expression to print anything from matching search
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=269906 --- Comment #6 from Mina Galić --- n.b.: this is in reference to https://reviews.freebsd.org/D39167 thank you very much for your investigation! -- You are receiving this mail because: You are the assignee for the bug.
[Bug 269906] dtrace requires empty expression to print anything from matching search
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=269906 Mina Galić changed: What|Removed |Added Status|Open|Closed Resolution|--- |Overcome By Events --- Comment #4 from Mina Galić --- i have bigger fish to fry, and limited time, so I'm okay with this line of action. but, yeah, basically, doing the thing that awk doesq, or giving a better hint in the error would be cool -- You are receiving this mail because: You are the assignee for the bug.
[Bug 269906] dtrace requires empty expression to print anything from matching search
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=269906
Mark Johnston changed:
What|Removed |Added
CC||ma...@freebsd.org
--- Comment #3 from Mark Johnston ---
>From what I can see this isn't a bug, but rather a request to change D's
grammar to make ' //' equivalent to ' //{}'.
This isn't unreasonable, but without a patch or a volunteer to work on this I'm
inclined to close the report.
--
You are receiving this mail because:
You are the assignee for the bug.
[Bug 269906] dtrace_kinst: dtrace requires empty expression to print anything from matching search
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=269906 --- Comment #2 from Mina Galić --- I was not the one to rename it ;) 0mp asked me to open a bug, and then renamed it -- You are receiving this mail because: You are the assignee for the bug.
[Bug 269906] dtrace_kinst: dtrace requires empty expression to print anything from matching search
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=269906
Christos Margiolis changed:
What|Removed |Added
CC||chris...@margiolis.net
--- Comment #1 from Christos Margiolis ---
(In reply to Mina Galić from comment #0)
A predicate requires a body, this is not a kinst bug.
FBT does the same thing:
# dtrace -n 'fbt::virtqueue_poll: /cpu == 1/'
dtrace: invalid probe specifier fbt::virtqueue_poll: /cpu == 1/: syntax error
near end of input
# dtrace -n 'fbt::virtqueue_poll: /cpu == 1/{}'
dtrace: description 'kinst::virtqueue_poll: ' matched 2 probes
--
You are receiving this mail because:
You are the assignee for the bug.
[Bug 269906] dtrace_kinst: dtrace requires empty expression to print anything from matching search
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=269906 Mateusz Piotrowski <0...@freebsd.org> changed: What|Removed |Added Assignee|b...@freebsd.org|dtr...@freebsd.org -- You are receiving this mail because: You are the assignee for the bug.
[Bug 232675] dtrace: "failed to compile script" when more than 2^15 distinct types are in CTF info
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=232675 Mike changed: What|Removed |Added CC||mike-wes...@hotmail.com --- Comment #51 from Mike --- (In reply to Kurt Jaeger from comment #34) I just got this exact same error. ===> Building for tcl86-8.6.13 /usr/sbin/dtrace -h -o tclDTrace.h -s /usr/ports/lang/tcl86/work/tcl8.6.13/generic/tclDTrace.d dtrace: failed to compile script /usr/ports/lang/tcl86/work/tcl8.6.13/generic/tclDTrace.d: "/usr/lib/dtrace/ipfw.d", line 1: syntax error near "in_addr_t" *** [tclDTrace.h] Error code 1 make[2]: stopped in /usr/ports/lang/tcl86/work/tcl8.6.13/unix 1 error make[2]: stopped in /usr/ports/lang/tcl86/work/tcl8.6.13/unix ===> Compilation failed unexpectedly. Running TrueNAS 13.1-RELEASE-p4 -- You are receiving this mail because: You are on the CC list for the bug.
[Bug 267619] dtrace: Compiler produces bogus error message: internal error -- token type 316 is not a valid D compilation token
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=267619 Kubilay Kocak changed: What|Removed |Added Assignee|b...@freebsd.org|dtr...@freebsd.org Severity|Affects Only Me |Affects Some People Summary|dtrace compiler produces a |dtrace: Compiler produces |bogus error message |bogus error message: ||internal error -- token ||type 316 is not a valid D ||compilation token CC||dtr...@freebsd.org Status|New |Open Keywords||needs-qa Flags||mfc-stable13?, ||mfc-stable12? -- You are receiving this mail because: You are the assignee for the bug. You are on the CC list for the bug.
[Bug 263858] dtrace: Fails to compile script on main: operator -> cannot be applied to a forward declaration: no struct ip_fw_args definition is available
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=263858 Tomoaki AOKI changed: What|Removed |Added Status|Open|Closed Resolution|--- |Not A Bug --- Comment #12 from Tomoaki AOKI --- Closing. Not a bug but mis-setting on /etc/make.conf. Sorry for the noise. Hope this helps for someone bitten by the same mis-setting. -- You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the bug.
[Bug 263858] dtrace: Fails to compile script on main: operator -> cannot be applied to a forward declaration: no struct ip_fw_args definition is available
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=263858
--- Comment #11 from Tomoaki AOKI ---
(In reply to Tomoaki AOKI from comment #10)
Problem solved.
I've missed one setting in /etc/make.conf only on main, which I believed I've
commented out several years ago, when sys/amd64/conf/GENERIC-NODEBUG was
introduced and switching to use it.
.if ${.CURDIR:M/usr/src/*}
DEBUG_FLAGS=
.endif
Commentig out this whole part solved the issue.
bz@'s script ran OK and java/openjdk11 builds fine.
The problematic part was one of the settings to disable debug settings.
I thought it also is needed to disable debug on -current ATM.
Remaining question is that why I've never bitten by this before, IIRC.
Anyway, I'll close this. Sorry for the noise.
--
You are receiving this mail because:
You are the assignee for the bug.
You are on the CC list for the bug.
[Bug 263858] dtrace: Fails to compile script on main: operator -> cannot be applied to a forward declaration: no struct ip_fw_args definition is available
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=263858 --- Comment #10 from Tomoaki AOKI --- (In reply to Mark Johnston from comment #8) > Oh. How did you build ipfw.ko? Did you build it as a standalone module, or > as > part of a buildkernel? In the latter case, do you have "makeoptions > WITH_CTF=1" in the kernel configuration? As part of buildkernel process. I basically don't build modules in base standalone. And my kernel configuration on main is as below, stripping comments. include GENERIC-NODEBUG ident confname options CAM_IOSCHED_DYNAMIC As GENERIC-NODEBUG includes GENERIC, and /usr/src/sys/conf/std.nodebug doesn't seem to overwrite the makeoptions, there should be, theoretically, "makeoptions WITH_CTF=1". Kerel configuration on stable/13 is different, as stable/13 doesn't have GENERIC-NODEBUG to include. I've copied old-style GENERIC-NODEBUG from main (current, ATM) and applied minimal change (change ident line and add options CAM_IOSCHED_DYNAMIC). include GENERIC ident confname nooptions DDB nooptions GDB nooptions INVARIANTS nooptions INVARIANT_SUPPORT nooptions WITNESS nooptions WITNESS_SKIPSPIN nooptions DEADLKRES options CAM_IOSCHED_DYNAMIC -- You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the bug.
[Bug 263858] dtrace: Fails to compile script on main: operator -> cannot be applied to a forward declaration: no struct ip_fw_args definition is available
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=263858 --- Comment #9 from Tomoaki AOKI --- Created attachment 233840 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=233840=edit Output from `ctfdump -ht /boot/kernel/ipfw.ko` on stable/13 Output from `ctfdump -ht /boot/kernel/ipfw.ko` on stable/13 at git: 3c01fdcfc161b06732b0762e37d1beca4a1f214d, amd64. dtrace works fine on stable/13. -- You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the bug.
[Bug 263858] dtrace: Fails to compile script on main: operator -> cannot be applied to a forward declaration: no struct ip_fw_args definition is available
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=263858 --- Comment #8 from Mark Johnston --- (In reply to Tomoaki AOKI from comment #7) Oh. How did you build ipfw.ko? Did you build it as a standalone module, or as part of a buildkernel? In the latter case, do you have "makeoptions WITH_CTF=1" in the kernel configuration? -- You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the bug.
[Bug 263858] dtrace: Fails to compile script on main: operator -> cannot be applied to a forward declaration: no struct ip_fw_args definition is available
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=263858 --- Comment #7 from Tomoaki AOKI --- (In reply to Mark Johnston from comment #6) > There is one similar problem which was fixed recently by commit 6e563a1b608. > Are you sure that you have an updated libctf.so? Sure. My last update at git: 2f44ad86f5553edb9e7854767424f22ba132ee92 was a clean rebuild. Backup /usr/obj/usr/src/amd64.amd64/sys/(confname)/version, delete everything under /usr/obj, then restore /usr/obj/usr/src/amd64.amd64/sys/(confname)/version to keep build No. monotonic. > Also I presume that you have ipfw.ko loaded; can you attach output from > "ctfdump -ht /path/to/ipfw.ko"? Yes. ipfw.ko is loaded as I configure it via /etc/rc.conf. The output from `ctfdump -ht /boot/kernel/ipfw.ko` are as below. No difference between regular user (in wheel group) and root. % ctfdump -ht /boot/kernel/ipfw.ko ctfdump: /boot/kernel/ipfw.ko does not contain .SUNW_ctf data : No error: 0 The above output seems to be via stderr. -- You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the bug.
[Bug 263858] dtrace: Fails to compile script on main: operator -> cannot be applied to a forward declaration: no struct ip_fw_args definition is available
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=263858 --- Comment #6 from Mark Johnston --- I'm not able to reproduce the problem at commit c6df2176038. There is one similar problem which was fixed recently by commit 6e563a1b608. Are you sure that you have an updated libctf.so? Also I presume that you have ipfw.ko loaded; can you attach output from "ctfdump -ht /path/to/ipfw.ko"? -- You are receiving this mail because: You are the assignee for the bug. You are on the CC list for the bug.
[Bug 263858] dtrace: Fails to compile script on main: operator -> cannot be applied to a forward declaration: no struct ip_fw_args definition is available
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=263858 --- Comment #5 from Tomoaki AOKI --- (In reply to Mark Johnston from comment #4) I've tried bz@'s script for testing iwlwifi at revs in NG list below with no success. The rev I encountered java/openjdk11 build error is unclear, but any of the revs in NG list below. The last successful java/openjdk11 is not recorded. Sorry. But maybe at... *Unclear (bz@'s script was not yet provided) but possibly OK rev.: a35bdd4489b97f14cb46ebd0f5354685e4488af3 tcp: add sysctl interface for setting socket options or e01e8f911b935eabcc35b4d121951e4e21042ee5 freebsd-update: improve BE creation feature *Known to be NG revs: 32c3e0f04921f1641c431433cf00ab2a1d9c100e nfscl: Clean up the code by removing unused arguments b75644771aa8bd362b9d22bc66c6bd6cc2beaf8a Add nullfs specific nocache option. 350668eb09a274436922fd580cd958c6a8a7eb25 rpc.tlsservd: Delete set but unused variable 350668eb09a274436922fd580cd958c6a8a7eb25 rpc.tlsservd: Delete set but unused variable 9fb40baf60435c000415429220c57c754ce318fd cam_periph: Return ENXIO when peripheral is invalidated f44280bf5fbb0599871612e9286407981ad4aaa3 libz: update the upgrade instructions to reflect reality 1599fc904d35cfa8eecad92818d1f4b55de6818f iosched: Move bio_next() inside of the CAM_IOSCHED_DYNAMIC ifdef 9a3583bfbd1740a158b3916432286190e0f2bf60 OpenSSL: Merge OpenSSL 1.1.1o 9f580526e45a28fdfabe1aa58798ad3883690af0 ibcore: Remove set, but not used variable. 2f44ad86f5553edb9e7854767424f22ba132ee92 dmesg: Better wording from review -- You are receiving this mail because: You are the assignee for the bug. You are on the CC list for the bug.
[Bug 263858] dtrace: Fails to compile script on main: operator -> cannot be applied to a forward declaration: no struct ip_fw_args definition is available
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=263858 Mark Johnston changed: What|Removed |Added CC||ma...@freebsd.org --- Comment #4 from Mark Johnston --- Which revision of main are you testing? -- You are receiving this mail because: You are the assignee for the bug. You are on the CC list for the bug.
[Bug 263858] dtrace: Fails to compile script on main: operator -> cannot be applied to a forward declaration: no struct ip_fw_args definition is available
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=263858
--- Comment #3 from Tomoaki AOKI ---
(In reply to Tomoaki AOKI from comment #2)
Tried a bit more.
The affected scripts of java/openjdk11 are generated on early build stage.
Not yet exist on extract, patch nor configure stage.
Searching *.d files on ${WRKDIR} at extract stage resulted in:
/usr/ports/java/openjdk11/work/jdk11u-jdk-11.0.15-10-1/src/hotspot/os/solaris/dtrace/jhelper.d
/usr/ports/java/openjdk11/work/jdk11u-jdk-11.0.15-10-1/src/hotspot/os/posix/dtrace/hotspot.d
/usr/ports/java/openjdk11/work/jdk11u-jdk-11.0.15-10-1/src/hotspot/os/posix/dtrace/hotspot_jni.d
/usr/ports/java/openjdk11/work/jdk11u-jdk-11.0.15-10-1/src/hotspot/os/posix/dtrace/hs_private.d
/usr/ports/java/openjdk11/work/jdk11u-jdk-11.0.15-10-1/test/hotspot/jtreg/compiler/codecache/dtrace/SegmentedCodeCacheDtraceTestScript.d
All files, including anything existing at extract stage seems to have the same
time stamp of release.
Looking into upstream github, above files seems to be 5 years old. [1]
So they would not be modified, unless following generation process is changed.
But looking into further beyonds me, unfortunately.
So what I can provide currently is what I wrote my previous post.
[1] https://github.com/openjdk/jdk/tree/master/src/hotspot/os/posix/dtrace
--
You are receiving this mail because:
You are the assignee for the bug.
You are on the CC list for the bug.
[Bug 263858] dtrace: Fails to compile script on main: operator -> cannot be applied to a forward declaration: no struct ip_fw_args definition is available
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=263858 --- Comment #2 from Tomoaki AOKI --- (In reply to Kubilay Kocak from comment #1) IIRC, this didn't happen on previous java/openjdk11 update (bump), dated at 2022-02-12 04:28:15 +. ports main git: 399e3772d37e1ca597304d7e6784d4ee410ba869 dtrace-related portion on ports Makefile doesn't change with most recent commit, dated at 2022-05-05 01:50:04 +. ports main git: ec8ecb5b4a24746692cfd03a1f7bafeabe6409f6 Note that whether upstream modified the script on update or not is not checked. (I've looked into ports side only.) Both built fine on stable/13. Disabling dtrace by forcibly adding --disable-dtrace to CONFIGURE_ARGS allowed build, so the problem is dtrace-related only. For bz@'s script, I have no OK data point on main. But no faulure on stable/13. -- You are receiving this mail because: You are the assignee for the bug. You are on the CC list for the bug.
[Bug 263858] dtrace: Fails to compile script on main: operator -> cannot be applied to a forward declaration: no struct ip_fw_args definition is available
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=263858 Kubilay Kocak changed: What|Removed |Added Flags||mfc-stable13-, ||mfc-stable12- Keywords||needs-qa CC||dtr...@freebsd.org Summary|dtrace: Fail to compile |dtrace: Fails to compile |script on main |script on main: operator -> ||cannot be applied to a ||forward declaration: no ||struct ip_fw_args ||definition is available Assignee|b...@freebsd.org|dtr...@freebsd.org Status|New |Open --- Comment #1 from Kubilay Kocak --- Are you able to bisect or further narrow down the commit/regression window? -- You are receiving this mail because: You are the assignee for the bug. You are on the CC list for the bug.
[Bug 262412] DTrace failed to run when ipfw loaded
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=262412 Mark Johnston changed: What|Removed |Added CC||ma...@freebsd.org Assignee|dtr...@freebsd.org |ma...@freebsd.org -- You are receiving this mail because: You are the assignee for the bug.
[Bug 232675] dtrace: "failed to compile script" when more than 2^15 distinct types are in CTF info
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=232675 Mark Johnston changed: What|Removed |Added Resolution|--- |FIXED Status|In Progress |Closed --- Comment #50 from Mark Johnston --- (In reply to Mark Johnston from comment #44) These are now merged to stable/13. -- You are receiving this mail because: You are on the CC list for the bug.
[Bug 262412] DTrace failed to run when ipfw loaded
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=262412 trond.endres...@ximalas.info changed: What|Removed |Added CC||trond.endres...@ximalas.inf ||o --- Comment #1 from trond.endres...@ximalas.info --- Everything DTrace capable must have their DTrace support disabled on systems running CURRENT and using ipfw. This poses a challenge for java/openjdk11 where there is no easy way of disabling DTrace. See https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=262809 -- You are receiving this mail because: You are the assignee for the bug.
[Bug 232675] dtrace: "failed to compile script" when more than 2^15 distinct types are in CTF info
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=232675 --- Comment #49 from Marek Zarychta --- (In reply to Mark Johnston from comment #47) >That would seem to suggest that you have only dtrace.ko loaded, and not >fbt.ko, >sdt.ko etc.. Try loading dtraceall.ko instead. Thanks for the clue and for fixing this. I haven't used DTrace(1) for a while. I am sorry for making noise here. -- You are receiving this mail because: You are on the CC list for the bug.
[Bug 232675] dtrace: "failed to compile script" when more than 2^15 distinct types are in CTF info
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=232675 --- Comment #48 from Marek Zarychta --- *** Bug 262961 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are on the CC list for the bug.
[Bug 232675] dtrace: "failed to compile script" when more than 2^15 distinct types are in CTF info
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=232675 --- Comment #47 from Mark Johnston --- (In reply to Marek Zarychta from comment #46) That would seem to suggest that you have only dtrace.ko loaded, and not fbt.ko, sdt.ko etc.. Try loading dtraceall.ko instead. -- You are receiving this mail because: You are on the CC list for the bug.
[Bug 232675] dtrace: "failed to compile script" when more than 2^15 distinct types are in CTF info
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=232675 Marek Zarychta changed: What|Removed |Added CC||zarych...@plan-b.pwste.edu. ||pl --- Comment #46 from Marek Zarychta --- I am trying to run dtrace(1) on: FreeBSD 14.0-CURRENT #7 main-n253931-9b597132aea: Thu Mar 24 10:24:28 CET 2022 #dtrace -l ID PROVIDERMODULE FUNCTION NAME 1 dtrace BEGIN 2 dtrace END 3 dtrace ERROR what still seems to be not correct while # ctfdump -S /boot/kernel/kernel | grep "total number of types" total number of types = 32821 -- You are receiving this mail because: You are on the CC list for the bug.
[Bug 232675] dtrace: "failed to compile script" when more than 2^15 distinct types are in CTF info
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=232675 Mark Johnston changed: What|Removed |Added CC||ksbeat...@lbl.gov --- Comment #45 from Mark Johnston --- *** Bug 227312 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are on the CC list for the bug.
[Bug 232675] dtrace: "failed to compile script" when more than 2^15 distinct types are in CTF info
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=232675
Mark Johnston changed:
What|Removed |Added
Status|Open|In Progress
--- Comment #44 from Mark Johnston ---
This is finally fixed in main, by introducing a new version of the CTF format
which lifts the type ID limitation (now one can have up to 2^{31} types, which
ought to be enough for anybody. The MFC period is somewhat conservative since
it was a large changeset.
https://cgit.freebsd.org/src/commit/?id=cb6f7225629301d3179f6e9f6d3be4d80f57a31f
https://cgit.freebsd.org/src/commit/?id=d7412bcac8a970542dc752f8717a38593d4192ec
https://cgit.freebsd.org/src/commit/?id=bdf290cd3e1a69d41c2f8bb60bd415cfa78adba2
https://cgit.freebsd.org/src/commit/?id=a6fb86917362e3f6d24e95e940e80845c2cfde8a
https://cgit.freebsd.org/src/commit/?id=8dbae4ce32bde42daee050ccfceee5eb2d306786
https://cgit.freebsd.org/src/commit/?id=d9175438c0e77ef2b400601aa8cf8098c82a77a7
https://cgit.freebsd.org/src/commit/?id=994297b01b98816bea1abf45ae4bac1bc69ee7a0
https://cgit.freebsd.org/src/commit/?id=cab9382a2cdf88b3027370cbdf73b095598eb7c1
https://cgit.freebsd.org/src/commit/?id=2d5d2a986ce1a93b8567dbdf3f80bc2b545d6998
--
You are receiving this mail because:
You are on the CC list for the bug.
[Bug 262439] dtrace tests: common.ip.t_dtrace_contrib.* cannot locate get.ipv4remote.pl
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=262439 Bug ID: 262439 Summary: dtrace tests: common.ip.t_dtrace_contrib.* cannot locate get.ipv4remote.pl Product: Base System Version: CURRENT Hardware: Any OS: Any Status: New Severity: Affects Only Me Priority: --- Component: tests Assignee: dtr...@freebsd.org Reporter: lw...@freebsd.org CC: test...@freebsd.org Those test cases cannot locate get.ipv4remote.pl and result expected failure and skipped in tests: tst.ipv4remoteicmp.ksh tst.ipv4remotesctp.ksh tst.ipv4remotetcp.ksh tst.ipv4remoteudp.ksh tst.ipv4remoteudplite.ksh tst.remotesctpstate.ksh tst.remotetcpstate.ksh cddl/contrib/opensolaris/cmd/dtrace/test/tst/common/ip/get.ipv4remote.pl is not installed and may need to adjust the path in those ksh scripts. The same case for get.ipv6remote.pl, used by tst.ipv6remoteicmp.ksh -- You are receiving this mail because: You are the assignee for the bug.
[Bug 262416] Failing dtrace test: common.ip.t_dtrace_contrib.{tst_ipv4localsctp_ksh,tst_localsctpstate_ksh}
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=262416 Li-Wen Hsu changed: What|Removed |Added Assignee|dtr...@freebsd.org |lw...@freebsd.org --- Comment #2 from Li-Wen Hsu --- https://github.com/freebsd/freebsd-ci/commit/fedd4ce5b5246c8e88515fade5f78cf6672b7f3e -- You are receiving this mail because: You are the assignee for the bug.
[Bug 262416] Failing dtrace test: common.ip.t_dtrace_contrib.{tst_ipv4localsctp_ksh,tst_localsctpstate_ksh}
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=262416 Li-Wen Hsu changed: What|Removed |Added Status|New |In Progress --- Comment #1 from Li-Wen Hsu --- This is because of we removed SCTP from GENERIC and these tests need it. src e64080e79c53f2952c5a77c6402cd2473cd45d8c -- You are receiving this mail because: You are the assignee for the bug.
[Bug 262415] Failing dtrace test: common.funcs.t_dtrace_contrib.tst_system_d
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=262415 Li-Wen Hsu changed: What|Removed |Added Assignee|dtr...@freebsd.org |lw...@freebsd.org Resolution|--- |FIXED Status|New |Closed -- You are receiving this mail because: You are the assignee for the bug.
[Bug 262415] Failing dtrace test: common.funcs.t_dtrace_contrib.tst_system_d
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=262415 --- Comment #2 from commit-h...@freebsd.org --- A commit in branch stable/13 references this bug: URL: https://cgit.FreeBSD.org/src/commit/?id=937d08454b3c5dea35f6ddc9692825a328e6c0c3 commit 937d08454b3c5dea35f6ddc9692825a328e6c0c3 Author: Li-Wen Hsu AuthorDate: 2022-03-09 03:39:12 + Commit: Li-Wen Hsu CommitDate: 2022-03-09 03:42:23 + dtrace tests: Fix expected outout for tst.system.d This is follow up of d500a85e640d1cd270747c12e17c511b53864436 PR: 262415 Sponsored by: The FreeBSD Foundation (cherry picked from commit 16e02ae401ebd9aa7d47f46dc4905f4f8add70a8) .../cmd/dtrace/test/tst/common/funcs/tst.system.d.out| 12 ++-- 1 file changed, 6 insertions(+), 6 deletions(-) -- You are receiving this mail because: You are the assignee for the bug.
[Bug 262415] Failing dtrace test: common.funcs.t_dtrace_contrib.tst_system_d
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=262415 --- Comment #1 from commit-h...@freebsd.org --- A commit in branch main references this bug: URL: https://cgit.FreeBSD.org/src/commit/?id=16e02ae401ebd9aa7d47f46dc4905f4f8add70a8 commit 16e02ae401ebd9aa7d47f46dc4905f4f8add70a8 Author: Li-Wen Hsu AuthorDate: 2022-03-09 03:39:12 + Commit: Li-Wen Hsu CommitDate: 2022-03-09 03:39:12 + dtrace tests: Fix expected outout for tst.system.d This is follow up of d500a85e640d1cd270747c12e17c511b53864436 PR: 262415 Sponsored by: The FreeBSD Foundation .../cmd/dtrace/test/tst/common/funcs/tst.system.d.out| 12 ++-- 1 file changed, 6 insertions(+), 6 deletions(-) -- You are receiving this mail because: You are the assignee for the bug.
[Bug 262416] Failing dtrace test: common.ip.t_dtrace_contrib.{tst_ipv4localsctp_ksh,tst_localsctpstate_ksh}
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=262416
Bug ID: 262416
Summary: Failing dtrace test:
common.ip.t_dtrace_contrib.{tst_ipv4localsctp_ksh,tst_
localsctpstate_ksh}
Product: Base System
Version: CURRENT
Hardware: Any
OS: Any
Status: New
Severity: Affects Only Me
Priority: ---
Component: bin
Assignee: dtr...@freebsd.org
Reporter: lw...@freebsd.org
CC: test...@freebsd.org
common.ip.t_dtrace_contrib.tst_ipv4localsctp_ksh
common.ip.t_dtrace_contrib.tst_localsctpstate_ksh
have been failing since:
https://ci.freebsd.org/view/Test/job/FreeBSD-main-amd64-dtrace_test/12133/
src r363254 (d272016da471691b2598ac2d76f9c6c960a1c9b8)
https://ci.freebsd.org/view/Test/job/FreeBSD-main-amd64-dtrace_test/15687/testReport/common.ip/t_dtrace_contrib/tst_ipv4localsctp_ksh/
https://ci.freebsd.org/view/Test/job/FreeBSD-main-amd64-dtrace_test/15687/testReport/common.ip/t_dtrace_contrib/tst_localsctpstate_ksh/
Both failed with:
dtrace: failed to compile script /dev/stdin: line 1: probe description
sctp:::send does not match any probes
--
You are receiving this mail because:
You are the assignee for the bug.
[Bug 262415] Failing dtrace test: common.funcs.t_dtrace_contrib.tst_system_d
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=262415 Bug ID: 262415 Summary: Failing dtrace test: common.funcs.t_dtrace_contrib.tst_system_d Product: Base System Version: CURRENT Hardware: Any OS: Any Status: New Severity: Affects Only Me Priority: --- Component: bin Assignee: dtr...@freebsd.org Reporter: lw...@freebsd.org common.funcs.t_dtrace_contrib.tst_system_d has been failing since: https://ci.freebsd.org/view/Test/job/FreeBSD-main-amd64-dtrace_test/13912/ src b0df36580d5b0df67a0f58ded8f6356b268f7f71 https://ci.freebsd.org/view/Test/job/FreeBSD-main-amd64-dtrace_test/13912/testReport/junit/common.funcs/t_dtrace_contrib/tst_system_d/ # Error Message atf-check failed; see the output of the test for details # Standard Output Executing command [ /usr/tests/cddl/usr.sbin/dtrace/common/funcs/../../dtest /usr/tests/cddl/usr.sbin/dtrace/common/funcs/tst.system.d ] # Standard Error Test case metadata -- allowed_architectures is empty allowed_platforms is empty description = DTrace test common/funcs/tst.system.d has_cleanup = false is_exclusive = false required_configs is empty required_disk_space = 0 required_files is empty required_memory = 0 required_programs is empty required_user is empty timeout = 300 Timing information -- Start time: 2021-04-23T19:05:53.432868Z End time: 2021-04-23T19:05:53.598022Z Duration: 0.165s Original stderr --- Fail: incorrect exit status: 1, expected: 0 stdout: stderr: test tst.system.d failed: test output mismatch test stdout: -- foo 9 -2 PING 127.0.0.1 (127.0.0.1): 56 data bytes --- 127.0.0.1 ping statistics --- 1 packets transmitted, 1 packets received, 0.0% packet loss 10 PING 127.0.0.1 (127.0.0.1): 56 data bytes --- 127.0.0.1 ping statistics --- 1 packets transmitted, 1 packets received, 0.0% packet loss 11 PING 127.0.0.1 (127.0.0.1): 56 data bytes --- 127.0.0.1 ping statistics --- 1 packets transmitted, 1 packets received, 0.0% packet loss 12 -- -- You are receiving this mail because: You are the assignee for the bug.
[Bug 262412] DTrace failed to run when ipfw loaded
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=262412
Bug ID: 262412
Summary: DTrace failed to run when ipfw loaded
Product: Base System
Version: CURRENT
Hardware: Any
OS: Any
Status: New
Severity: Affects Only Me
Priority: ---
Component: bin
Assignee: dtr...@freebsd.org
Reporter: lw...@freebsd.org
CC: i...@freebsd.org
https://artifact.ci.freebsd.org/snapshot/main/23210c9f42af94dc6bcdae3996d8a3d010dd6bfe/amd64/amd64/disk-test.img.zst
FreeBSD 14.0-CURRENT FreeBSD 14.0-CURRENT #0 23210c9: Mon Mar 7 23:39:03 UTC
2022 r...@freebsd-main-amd64-build.jail.ci.freebsd.org:/usr/ob
j/usr/src/amd64.amd64/sys/GENERIC amd64
root@:/ # dtrace -n 'syscall:::entry { @[execname] = count(); }' -c /bin/ls
dtrace: invalid probe specifier syscall:::entry { @[execname] = count(); }:
"/usr/lib/dtrace/ipfw.d", line 1: m is not a member of struct ip_fw_args
--
You are receiving this mail because:
You are the assignee for the bug.
[Bug 261999] dtruss: Fails to run: dtrace: invalid probe specifier => lstat* not found
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=261999 Kubilay Kocak changed: What|Removed |Added Keywords||needs-qa Assignee|b...@freebsd.org|dtr...@freebsd.org Summary|[dtruss] dtrace: invalid|dtruss: Fails to run: |probe specifier => lstat* |dtrace: invalid probe |not found |specifier => lstat* not ||found CC||dtr...@freebsd.org Severity|Affects Only Me |Affects Some People Status|New |Open -- You are receiving this mail because: You are the assignee for the bug. You are on the CC list for the bug.
[Bug 232675] dtrace: "failed to compile script" when more than 2^15 distinct types are in CTF info
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=232675 --- Comment #43 from Dani --- If helpfull: Here are the stats from the same custom kernelconfig with FBSD 12.2: - CTF Statistics - total number of data objects= 31042 total number of functions = 33926 total number of function arguments = 82409 maximum argument list length= 22 average argument list length= 2.43 total number of types = 31478 total number of integers= 77 total number of floats = 0 total number of pointers= 7668 total number of arrays = 3340 total number of func types = 2091 total number of structs = 10738 total number of unions = 621 total number of enums = 886 total number of forward tags= 51 total number of typedefs= 5251 total number of volatile types = 55 total number of const types = 580 total number of restrict types = 0 total number of unknowns (holes)= 120 total number of struct members = 79250 maximum number of struct members= 248 total size of all structs = 19349614 maximum size of a struct= 2971720 average number of struct members= 7.38 average size of a struct= 1801.98 total number of union members = 2151 maximum number of union members = 90 total size of all unions= 133604 maximum size of a union = 41576 average number of union members = 3.46 average size of a union = 215.14 total number of enum members= 9025 maximum number of enum members = 1023 average number of enum members = 10.19 total number of unique strings = 67943 bytes of string data= 982977 maximum string length = 81 average string length = 14.47 Here's the kernelconfig (yes some stuff is double with GENERIC, we just want to make sure these options are set): include GENERIC ident CUSTOM options DDB options IPFIREWALL options IPFIREWALL_VERBOSE options IPFIREWALL_VERBOSE_LIMIT=5 options IPFIREWALL_DEFAULT_TO_ACCEPT options IPDIVERT device pf device pflog device pfsync device enc device cpuctl device tuntap -- You are receiving this mail because: You are on the CC list for the bug.
[Bug 232675] dtrace: "failed to compile script" when more than 2^15 distinct types are in CTF info
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=232675 --- Comment #40 from Kubilay Kocak --- @Mark Is there anything we can do, tests or otherwise, to make these build (ideally) or test (CI) time failures, so as to pick them up early and/or reduce or otherwise preclude false positives or user/environment specific build issues? -- You are receiving this mail because: You are on the CC list for the bug.
[Bug 232675] dtrace: "failed to compile script" when more than 2^15 distinct types are in CTF info
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=232675 --- Comment #39 from Mark Johnston --- (In reply to Kurt Jaeger from comment #38) I am not sure what the problem is, then. It's not the one from this PR, and I think you have the relevant libctf fixes (https://cgit.freebsd.org/src/commit/?id=105fd928b0b5b35ab529e5f6914788dc49582901 is the most recent), and I cannot reproduce the error by building either tcl86 or 87 with ipfw.ko loaded. If it's possible that your userland/kernel are out of sync, or you have an out-of-date /usr/lib/dtrace/ipfw.d, then I'd suggest updating everything. -- You are receiving this mail because: You are on the CC list for the bug.
[Bug 232675] dtrace: "failed to compile script" when more than 2^15 distinct types are in CTF info
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=232675 --- Comment #37 from Mark Johnston --- (In reply to Kurt Jaeger from comment #36) Could you please show ctfdump -S output? -- You are receiving this mail because: You are on the CC list for the bug.
[Bug 232675] dtrace: "failed to compile script" when more than 2^15 distinct types are in CTF info
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=232675 --- Comment #36 from Kurt Jaeger --- (In reply to Mark Johnston from comment #35) version: 225639e7db68: Tue Oct 19 13:10:59 CEST 2021 Can it be that the build problem is tcl86 specific ? There is PR#224857, which led me via PR#227312 to this PR. -- You are receiving this mail because: You are on the CC list for the bug.
[Bug 232675] dtrace: "failed to compile script" when more than 2^15 distinct types are in CTF info
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=232675 --- Comment #35 from Mark Johnston --- (In reply to Kurt Jaeger from comment #34) Which revision? Several libctf problems relating to ipfw.d have been fixed lately. I can build tcl with dtrace enabled on main at 28d1296. -- You are receiving this mail because: You are on the CC list for the bug.
[Bug 232675] dtrace: "failed to compile script" when more than 2^15 distinct types are in CTF info
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=232675 --- Comment #34 from Kurt Jaeger --- (In reply to Shane from comment #33) Still the same problem on 14.0: /usr/sbin/dtrace -h -o tclDTrace.h -s /wrkdirs/usr/ports/lang/tcl86/work/tcl8.6.12/generic/tclDTrace.d dtrace: failed to compile script /wrkdirs/usr/ports/lang/tcl86/work/tcl8.6.12/generic/tclDTrace.d: "/usr/lib/dtrace/ipfw.d", line 1: syntax error near "in_addr_t" *** [tclDTrace.h] Error code 1 -- You are receiving this mail because: You are on the CC list for the bug.
[Bug 258763] dtrace: "/usr/lib/dtrace/ipfw.d", line 1: cannot find type: struct ip_fw_args*: Conflicting type is already defined
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=258763 Mark Johnston changed: What|Removed |Added Assignee|dtr...@freebsd.org |ma...@freebsd.org Status|New |In Progress -- You are receiving this mail because: You are the assignee for the bug.
[Bug 258763] dtrace: "/usr/lib/dtrace/ipfw.d", line 1: cannot find type: struct ip_fw_args*: Conflicting type is already defined
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=258763 --- Comment #2 from commit-h...@freebsd.org --- A commit in branch main references this bug: URL: https://cgit.FreeBSD.org/ports/commit/?id=c8470cb1b3d20680cb79e42698175d4f38caa9fb commit c8470cb1b3d20680cb79e42698175d4f38caa9fb Author: David Vachulka AuthorDate: 2021-09-28 18:12:59 + Commit: Li-Wen Hsu CommitDate: 2021-09-28 18:17:24 + irc/dxirc: Update to 1.40.0 Change maintainer email PR: 258763 irc/dxirc/Makefile| 6 ++--- irc/dxirc/distinfo| 6 ++--- irc/dxirc/files/patch-CMakeLists.txt | 8 +++ irc/dxirc/files/patch-data_CMakeLists.txt | 12 +- irc/dxirc/files/patch-fox_CMakeLists.txt | 27 - irc/dxirc/files/patch-qt_CMakeLists.txt | 39 --- irc/dxirc/pkg-plist | 9 +++ 7 files changed, 71 insertions(+), 36 deletions(-) -- You are receiving this mail because: You are the assignee for the bug.
[Bug 258763] dtrace: "/usr/lib/dtrace/ipfw.d", line 1: cannot find type: struct ip_fw_args*: Conflicting type is already defined
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=258763 --- Comment #1 from commit-h...@freebsd.org --- A commit in branch main references this bug: URL: https://cgit.FreeBSD.org/src/commit/?id=819961c5808b053c626648e202dec42a19ebe7a6 commit 819961c5808b053c626648e202dec42a19ebe7a6 Author: Li-Wen Hsu AuthorDate: 2021-09-28 18:02:27 + Commit: Li-Wen Hsu CommitDate: 2021-09-28 18:02:27 + Temporarily skip sys.geom.class.multipath.failloop.failloop in CI This test case uses `dtrace -c` but it has some issues at the moment While here, add a checker for dtrace executes successfully or not to provide a more informative error message. PR: 258763 Sponsored by: The FreeBSD Foundation tests/sys/geom/class/multipath/failloop.sh | 7 +++ 1 file changed, 7 insertions(+) -- You are receiving this mail because: You are the assignee for the bug.
[Bug 258763] dtrace: "/usr/lib/dtrace/ipfw.d", line 1: cannot find type: struct ip_fw_args*: Conflicting type is already defined
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=258763 Li-Wen Hsu changed: What|Removed |Added CC||domagoj.sto...@gmail.com, ||k...@freebsd.org, ||ma...@freebsd.org Assignee|b...@freebsd.org|dtr...@freebsd.org -- You are receiving this mail because: You are the assignee for the bug.
[Bug 232675] dtrace: "failed to compile script" when more than 2^15 distinct types are in CTF info
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=232675 Shane changed: What|Removed |Added CC||free...@shaneware.biz --- Comment #33 from Shane --- I have run into this building perl5.32 and tcl86 in poudriere. tcl86 reports the fail as a syntax error. Both perl5.32 and tcl86 build on the host but fail in a matching poudriere jail. host stable/13 e284a6234ffb - both build from ports jail stable/13 e284a6234 - both fail jail 13.0 release - both fail jail 12.2 - both build -- You are receiving this mail because: You are on the CC list for the bug. ___ freebsd-dtrace@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-dtrace To unsubscribe, send any mail to "freebsd-dtrace-unsubscr...@freebsd.org"
[Bug 244823] DTrace test common.pid.t_dtrace_contrib.err_D_PROC_OFF_toobig_d fails after clang10 import
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=244823 Mark Johnston changed: What|Removed |Added Resolution|--- |DUPLICATE Status|Open|Closed --- Comment #1 from Mark Johnston --- *** This bug has been marked as a duplicate of bug 244732 *** -- You are receiving this mail because: You are on the CC list for the bug. ___ freebsd-dtrace@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-dtrace To unsubscribe, send any mail to "freebsd-dtrace-unsubscr...@freebsd.org"
[Bug 244053] `dtrace -c` causes program dumps core after somewhere between (r357694, r357701]
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=244053 Mark Johnston changed: What|Removed |Added Status|Open|Closed Resolution|--- |FIXED CC||ma...@freebsd.org --- Comment #5 from Mark Johnston --- I suspect this is fixed by r360979. The bug was exposed by an LLVM update I believe. Please re-open if it is reproducible with that revision. -- You are receiving this mail because: You are the assignee for the bug. You are on the CC list for the bug. ___ freebsd-dtrace@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-dtrace To unsubscribe, send any mail to "freebsd-dtrace-unsubscr...@freebsd.org"
[Bug 244053] `dtrace -c` causes program dumps core after somewhere between (r357694, r357701]
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=244053 --- Comment #4 from commit-h...@freebsd.org --- A commit references this bug: Author: lwhsu Date: Mon May 18 23:43:48 UTC 2020 New revision: 361229 URL: https://svnweb.freebsd.org/changeset/base/361229 Log: Revert 357780, `dtrace -c` has been fixed in head` PR: 244053 Sponsored by: The FreeBSD Foundation Changes: head/tests/sys/geom/class/multipath/failloop.sh -- You are receiving this mail because: You are the assignee for the bug. You are on the CC list for the bug. ___ freebsd-dtrace@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-dtrace To unsubscribe, send any mail to "freebsd-dtrace-unsubscr...@freebsd.org"
[Bug 244053] `dtrace -c` causes program dumps core after somewhere between (r357694, r357701]
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=244053 --- Comment #3 from Li-Wen Hsu --- (In reply to Alan Somers from comment #2) >From bisect in artifact, this is fixed somewhere between (r358152, r358178] -- You are receiving this mail because: You are the assignee for the bug. You are on the CC list for the bug. ___ freebsd-dtrace@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-dtrace To unsubscribe, send any mail to "freebsd-dtrace-unsubscr...@freebsd.org"
[Bug 244053] `dtrace -c` causes program dumps core after somewhere between (r357694, r357701]
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=244053 --- Comment #2 from Alan Somers --- I can't reproduce this failure locally at r360076M. Was it fixed, or is this crash only reproducible in the CI environment? -- You are receiving this mail because: You are the assignee for the bug. You are on the CC list for the bug. ___ freebsd-dtrace@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-dtrace To unsubscribe, send any mail to "freebsd-dtrace-unsubscr...@freebsd.org"
[Bug 244823] DTrace test common.pid.t_dtrace_contrib.err_D_PROC_OFF_toobig_d fails after clang10 import
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=244823 Li-Wen Hsu changed: What|Removed |Added Status|New |Open CC||d...@freebsd.org, ||dtr...@freebsd.org -- You are receiving this mail because: You are on the CC list for the bug. ___ freebsd-dtrace@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-dtrace To unsubscribe, send any mail to "freebsd-dtrace-unsubscr...@freebsd.org"
[Bug 244053] `dtrace -c` causes program dumps core after somewhere between (r357694, r357701]
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=244053 Kubilay Kocak changed: What|Removed |Added Keywords||crash, needs-qa, regression CC||dtr...@freebsd.org Severity|Affects Only Me |Affects Many People -- You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the bug. ___ freebsd-dtrace@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-dtrace To unsubscribe, send any mail to "freebsd-dtrace-unsubscr...@freebsd.org"
[Bug 244053] `dtrace -c` causes program dumps core after somewhere between (r357694, r357701]
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=244053 --- Comment #1 from commit-h...@freebsd.org --- A commit references this bug: Author: lwhsu Date: Tue Feb 11 22:21:22 UTC 2020 New revision: 357780 URL: https://svnweb.freebsd.org/changeset/base/357780 Log: Temporarily skip sys.geom.class.multipath.failloop.failloop in CI This case uses `dtrace -c` but it has some issues at the moment PR: 244053 Sponsored by: The FreeBSD Foundation Changes: head/tests/sys/geom/class/multipath/failloop.sh -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-dtrace@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-dtrace To unsubscribe, send any mail to "freebsd-dtrace-unsubscr...@freebsd.org"
[Bug 244053] `dtrace -c` causes program dumps core after somewhere between (r357694, r357701]
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=244053 Li-Wen Hsu changed: What|Removed |Added Assignee|b...@freebsd.org|dtr...@freebsd.org Status|New |Open -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-dtrace@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-dtrace To unsubscribe, send any mail to "freebsd-dtrace-unsubscr...@freebsd.org"
[Bug 232675] dtrace: "failed to compile script" when more than 2^15 distinct types are in CTF info
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=232675 Kubilay Kocak changed: What|Removed |Added See Also||https://bugs.freebsd.org/bu ||gzilla/show_bug.cgi?id=2426 ||89 -- You are receiving this mail because: You are on the CC list for the bug. ___ freebsd-dtrace@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-dtrace To unsubscribe, send any mail to "freebsd-dtrace-unsubscr...@freebsd.org"
[Bug 232675] dtrace: "failed to compile script" when more than 2^15 distinct types are in CTF info
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=232675 Mark Johnston changed: What|Removed |Added Blocks|242689 | Referenced Bugs: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=242689 [Bug 242689] sys.geom.class.multipath.failloop.failloop fails due to too many CTF entries -- You are receiving this mail because: You are on the CC list for the bug. ___ freebsd-dtrace@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-dtrace To unsubscribe, send any mail to "freebsd-dtrace-unsubscr...@freebsd.org"
[Bug 232675] dtrace: "failed to compile script" when more than 2^15 distinct types are in CTF info
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=232675 --- Comment #32 from Mark Johnston --- (In reply to Mark Johnston from comment #30) I spent some time digging into this; the problem appears to be that we define struct pmap, once for the PAE pmap and once for the non-PAE pmap, and this structure is embedded in struct vmspace, which results in bifurcation of the type graph. I'll try to find a way to fix this that isn't too ugly. -- You are receiving this mail because: You are on the CC list for the bug. ___ freebsd-dtrace@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-dtrace To unsubscribe, send any mail to "freebsd-dtrace-unsubscr...@freebsd.org"
