1452 DTrace buffer autoscaling should be less violentillumos/illumos-gate@6fb4854bed54ce82bd8610896b64ddebcd4af706This fixes the tst.resize1.d and tst.resize2.d DTrace tests, which havebeen fail
1452 DTrace buffer autoscaling should be less violentillumos/illumos-gate@6fb4854bed54ce82bd8610896b64ddebcd4af706This fixes the tst.resize1.d and tst.resize2.d DTrace tests, which havebeen failing since r261122 since they were causing dtrace(1) to attempt toallocate and use large amounts of memory, and get killed by the OOM killeras a result.MFC after: 1 month
show more ...
Bring back part of r249367 by adding DTrace's temporal option, which allowsusers to guarantee that the output of DTrace scripts will be time-ordered.This option is enabled by adding the line #pr
Bring back part of r249367 by adding DTrace's temporal option, which allowsusers to guarantee that the output of DTrace scripts will be time-ordered.This option is enabled by adding the line #pragma D option temporalto the beginning of a script, or by adding '-x temporal' to the arguments ofdtrace(1).This change fixes a bug in the original port of the temporal option. Thisbug was causing some assertions to fail, so they had been disabled; in thisrevision the assertions are working properly and are enabled.The DTrace version number has been bumped from 1.9.0 to 1.9.1 to reflectthe language change that's being introduced.This change corresponds to part of illumos-gate commit e5803b76927480: 3021 option for time-ordered output from dtrace(1M)Reviewed by: pfgObtained from: illumosMFC after: 1 month
DTrace: Revert r249367The following change from illumos brought caused DTrace topause in an interactive environment:3026 libdtrace should set LD_NOLAZYLOAD=1 to help the pid providerThis was n
DTrace: Revert r249367The following change from illumos brought caused DTrace topause in an interactive environment:3026 libdtrace should set LD_NOLAZYLOAD=1 to help the pid providerThis was not detected during testing because it doesn'taffect scripts.We shouldn't be changing the environment, especially since theLD_NOLAZYLOAD option doesn't apply to our (GNU) ld.Unfortunately the change from upstream was made in such a waythat it is very difficult to separate this change from theothers so, at least for now, it's better to just reverteverything.Reference:https://www.illumos.org/issues/3026Reported by: Navdeep Parhar and Mark Johnston
DTrace: option for time-ordered outputMerge changes from illumos:3021 option for time-ordered output from dtrace(1M)3022 DTrace: keys should not affect the sort order when sorting by value3023
DTrace: option for time-ordered outputMerge changes from illumos:3021 option for time-ordered output from dtrace(1M)3022 DTrace: keys should not affect the sort order when sorting by value3023 it should be possible to dereference dynamic variables3024 D integer narrowing needs some work3025 register leak in D code generation3026 libdtrace should set LD_NOLAZYLOAD=1 to help the pid providerThis brings yet another feature implemented in upstream DTrace.A complete description is available here:http://dtrace.org/blogs/ahl/2012/07/28/my-new-dtrace-favorite/This change bumps the DT_VERS_* number to 1.9.1 inaccordance to what is done in illumos.This change was somewhat complicated because upstream is mixed manychanges in an individual commit and some of the tests don't reallyapply to us.There are also appear to be differences in timestamping with Solarisso we had to workaround some assertions making sure no regressionhappened.Special thanks to Fabian Keil for changes and testing.Illumos Revisions: 13758:23432da34147Reference:https://www.illumos.org/issues/3021https://www.illumos.org/issues/3022https://www.illumos.org/issues/3023https://www.illumos.org/issues/3024https://www.illumos.org/issues/3025https://www.illumos.org/issues/1694Tested by: Fabian KeilObtained from: IllumosMFC after: 1 months
This commit was generated by cvs2svn to compensate for changes in r178476,which included commits to RCS files with non-trunk default branches.