Date: Mon, 25 Apr 2016 00:05:32 +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-RwtmlQTsVs@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=3D207735 --- Comment #5 from Mark Johnston <markj@FreeBSD.org> --- (In reply to Jan Beich from comment #4) Yes. Sorry, I've just been very busy with work. I've spent more time looking at the code, and I think raising DTRACE_FUNCNAMELEN isn't a bad way to address the problem. I said in comment 3 that a buffer of size DTRACE_FUNCNAMELEN is created for every single probe, but this isn't right. It's only used when passing probe descriptions between userland and = the kernel, for instance when running dtrace -l, or when creating an enabling. I'll look at DTrace memory usage with and without a change that doubles this constant. Assuming I haven't missed anything, the difference should not be significant. I'll also modify the DOF validation code so that we simply skip probes with excessively long function names. --=20 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-RwtmlQTsVs>