Hi,
I grabbed the Mono Preview 2.0 installer for OS X and wanted to test
new DTrace probes mentioned in Release Notes[1], but it did not work.
On the #mono IRC channel, I learned that DTrace probes in mono are not
enabled in the binary packages provided, since it would incur
performance penalty
Hi,
Am 02.08.2008 um 17:25 schrieb Boris Dušek:
I grabbed the Mono Preview 2.0 installer for OS X and wanted to test
new DTrace probes mentioned in Release Notes[1], but it did not work.
Just to be sure, how did you test? As described in mono's man page?
On the #mono IRC channel, I learned
On Sat, 2008-08-02 at 18:30 +0200, Andreas Färber wrote:
Not fully true, there is of course a minimal degradation (~5 nop
instructions on Solaris), but it should be hardly noticeable. I have
taken care to only call helper functions when the probe is active.
Was the answer on IRC in any
Hi,
Looking at dtrace.h, all the current probes seem to be in
non-critical code-paths, so they
are unlikely to have a perf impact. We could make --enable-dtrace=true
the default in HEAD,
so it gets some testing.
Zoltan
On Sat, Aug 2, 2008 at 7:16 PM, Geoff Norton
Zoltan,
I'm fine with this on trunk, but I still think barring any compelling
reason we should leave the branch as is.
-g
On Sat, 2008-08-02 at 19:20 +0200, Zoltan Varga wrote:
Hi,
Looking at dtrace.h, all the current probes seem to be in
non-critical code-paths, so they
are unlikely
Hi all,
Attached is slightly revised version of a patch that Owen Brady sent me.
Owen is the original author of the code that Mono's ASP.NET 2.0
implementation uses for processing *.browser files. The patch updates his
email in the copyright notices at the top of each file and removes some
files
