Date: Mon, 07 Mar 2016 03:44:22 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-dtrace@FreeBSD.org Subject: [Bug 207735] www/firefox: DTRACE no longer works since 41.0 Message-ID: <bug-207735-32976-cwIVQGKSCD@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-207735-32976@https.bugs.freebsd.org/bugzilla/> References: <bug-207735-32976@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=207735 Mark Johnston <markj@FreeBSD.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|New |In Progress --- Comment #3 from Mark Johnston <markj@FreeBSD.org> --- DTrace allows the function component of a probe to be up to DTRACE_FUNCNAMELEN - 1 == 127 bytes in length and rejects DOF sections containing functions longer than that. DTRACE_FUNCNAMELEN is embedded into a few structs, so fixing this is non-trivial. Doubling it would waste at least 128 bytes per probe, of which there are typically tens of thousands, and still only pushes the problem out. It's silly that DTrace imposes this limit at all. Constraints on provider and probe name lengths make sense, and the module component is generally a filename, so a limit is reasonable. But the function component is just a symbol name, and ELF doesn't impose a limit here AFAIK. I'll try to remove the limit. -- You are receiving this mail because: You are on the CC list for the bug.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-207735-32976-cwIVQGKSCD>