Date: Fri, 07 Apr 2017 10:44:56 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-bugs@FreeBSD.org Subject: [Bug 218452] I can cause an assertion with a dtrace script and when it does happen, dtrace fails until the module dtraceall is reloaded Message-ID: <bug-218452-8-kHTmFD8QLP@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-218452-8@https.bugs.freebsd.org/bugzilla/> References: <bug-218452-8@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=3D218452 Fabian Keil <fk@fabiankeil.de> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |fk@fabiankeil.de --- Comment #1 from Fabian Keil <fk@fabiankeil.de> --- In ElectroBSD I replaced this and another timestamp-related assertion with warnings: https://www.fabiankeil.de/sourcecode/electrobsd/ElectroBSD-r312620-6cfa243f= 1516/0129-dtrace_consume-Warn-if-cpu-cores-are https://www.fabiankeil.de/sourcecode/electrobsd/ElectroBSD-r312620-6cfa243f= 1516/0165-libdtrace-Replace-another-timestamp-related-assert-wi.diffn-t-com= pletely-in.diff Obviously that's not a real fix but in many cases the timestamp mismatch doesn't matter and in these cases it seemed preferable to prematurly aborting the trace and dumping core. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-218452-8-kHTmFD8QLP>