Hello,
I'm trying to measure the code coverage of a test suite. I noticed that
recently (Apr'15) cov and monocov were removed for log:coverage profiler.
When I'm running that profile on my tests using nunit-console. I got a
segmentation fault, see below. When using mprof-report, I do not get the
HI
I want to call the following constructor via the embedded API:
public CloudClient(Func filePathCallback)
All my other embedded method and constructor calls work okay but there is an
issue with this one - it is the only place I use a System.Func.
The API reports that a method cannot be found
Hi,
The "time went backwards" message is harmless and has been removed in
later Mono versions.
Could you have a look at the crash, Iain? (cc)
On Thu, Mar 3, 2016 at 2:00 PM, Antoine Cailliau
wrote:
> Hello,
>
> I'm trying to measure the code coverage of a test suite. I noticed that
> recently (
Great.
Let me know if you need something or if I can help.
Antoine
On 3 March 2016 at 17:10, Iain Holmes wrote:
> Hi,
>
> Yes, I’ll have a look into it now.
>
> iain
>
> > On 3 Mar 2016, at 2:44 pm, Alex Rønne Petersen wrote:
> >
> > Hi,
> >
> > The "time went backwards" message is harmless a
On 03.03.2016 14:36, Jonathan Mitchell wrote:
HI
I want to call the following constructor via the embedded API:
public CloudClient(Func filePathCallback)
All my other embedded method and constructor calls work okay but there is an issue
with this one - it is the only place I use a System.Func
HI Robert
Thanks for that.
I think you are right.
I call hundreds of methods that take Obj`1 arguments with out issue but I
see that I have had to construct a number of helper methods to deal with cases
of Obj`2 which failed signature resolution.
I presume that managed code execution doesn’t i
Hi Jonathan,
The JIT isn't using these functions for method look-ups.
mono_method_descs are mainly for embedders (and for
trivial method look-ups at some places inside the runtime).
They come handy when you want to get an overloaded
MonoMethod in C/C++:
easy:
desc = mono_method_desc_new (":Me
Hi All,
I'm seeing a rare hang in Socket.ReceiveFrom() where the receive timeout isn't
respected. What's also odd is then on the server side once this wedge occurs
the server gets the same packet that had been sent to it over and over and it
keeps responding to it endlessly - but the client nev