--- Vladimir Fedorov [EMAIL PROTECTED] escribió:
...if part of your project is to create your own
infrastructure than you can mimic your own code off
the code for the profiler callback. In particular
look at the emit_callhelper_prof2(...) macro in
fjitdef.h. This macro emits the code for the
It seems the problem is in the number of actual arguments.
Try to use
emit_callhelper(func);
instead of
emit_callhelper_prof2(func, CORINFO_PRUEBA, from,
to);
regards,
Alexei Nikitin
--- Vladimir Fedorov [EMAIL PROTECTED] escribió:
...if part of your project is to create your own
Miguel,
The assert you are triggering occurs because of a stack imbalance. For example if you
call some function which expects the caller to clean up the stack, but you don't do it
- you will get this assert. In this case the assert is cause by the fact that you are
using emit_callhelper_prof2
I've run into problems with Rotor's profiling interface while trying
some simple things, initially just replacing body of a tiny method
with an exact copy. I base my code on the sample profiler. I try the
same thing with the CLR and things work fine there. Here are the
problems:
- Some event mask
