On Sun, 2008-08-03 at 21:57 +0200, Andreas Färber wrote:
What I will be looking into next is method-enter/method-exit probes
for tracing managed function flow, but it seems more complicated (the
JIT would need to always emit a call to a helper function, supplying
it the data to
Ciao Massi,
Am 05.08.2008 um 08:23 schrieb Massimiliano Mantione:
On Sun, 2008-08-03 at 21:57 +0200, Andreas Färber wrote:
What I will be looking into next is method-enter/method-exit probes
for tracing managed function flow, but it seems more complicated (the
JIT would need to always emit
On Tue, 2008-08-05 at 12:26 +0200, Andreas Färber wrote:
IMO, the correct way of doing this would be to implement it in a
profiler module, and it's amazingly easy doing so.
[...]
I don't wish to replace or belittle your profiler work. I think the
two have different scopes and different
Hi,
Are you talking of the once announced binary snapshots of trunk
Mono.framework, so that you would make some Novell-internal setting to
configure with --enable-dtrace?
Or do you suggest me to change trunk's configure.in to enable DTrace
when specifically Mac OS X v10.5+ is detected and
Hi,
On mono HEAD, dtrace is now enabled under solaris and macosx if the
dtrace utility is
detected by configure.
Zoltan
On Sun, Aug 3, 2008 at 4:08 PM, Andreas Färber [EMAIL PROTECTED] wrote:
Hi,
Are you talking of the once announced binary snapshots of trunk
Hi,
Am 03.08.2008 um 16:52 schrieb Zoltan Varga:
On mono HEAD, dtrace is now enabled under solaris and macosx if the
dtrace utility is
detected by configure.
Looks okay to me.
In this form it would even allow to build with DTrace enabled on
pre-10 Solaris once the tool becomes available
Hi Andreas,
On Sat, Aug 2, 2008 at 6:30 PM, Andreas Färber [EMAIL PROTECTED] wrote:
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?
Hi Boris,
Am 03.08.2008 um 17:32 schrieb Boris Dušek:
On Sat, Aug 2, 2008 at 6:30 PM, Andreas Färber
[EMAIL PROTECTED] wrote:
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
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
13 matches
Mail list logo
