Hi,
I've used mono --profile… in the past with 2.10.x and did not have problems in
being able to run.I was trying to run profiling on an app again, this time
with 3.0.x. On both osx and linux, I get:
The 'log' profiler wasn't found in the main executable nor could it be loaded
from
Den 18-03-2013 20:59, Jonathan Shore skrev:
Hi,
I've used mono --profile... in the past with 2.10.x and did not have
problems in being able to run.I was trying to run profiling on an
app again, this time with 3.0.x. On both osx and linux, I get:
The 'log' profiler wasn't found in the
On 18/03/13 22:57, Esben Laursen wrote:
Den 18-03-2013 20:59, Jonathan Shore skrev:
Hi,
I've used mono --profile… in the past with 2.10.x and did not have
problems in being able to run.I was trying to run profiling on an
app again, this time with 3.0.x. On both osx and linux, I get:
The
I believe the GC related profiling options, like allocation tracking
or heap-shot, only work with sgen. The performance related options
work irrespective of the GC being used.
Alan
On 18 March 2013 23:17, Andres G. Aragoneses kno...@gmail.com wrote:
On 18/03/13 22:57, Esben Laursen wrote:
Den
You probably mean to do:
$ csharp -r:System.Core
using System.Linq;
var x = new int[] { 1,2,3,4,5,6 };
var y = (from i in x where i 4 select x).Skip(1).FirstOrDefault();
Ian
On Sun, Mar 17, 2013 at 06:44:25PM +, Jonathan Pryor wrote:
On Mar 17, 2013, at 11:54 AM, Dale Ragan
On Mar 18, 2013, at 4:33 AM, Ian Norton
ian.norton-bad...@thales-esecurity.com wrote:
You probably mean to do:
$ csharp -r:System.Core
That shouldn't be necessary at all; System.Core.dll should be in the default
assembly include set and `using System.Linq` should be in the default
I have an win32-application using an c# callback invoked from native code.
Running the programm normally seems to work.
Running with debugger makes the program crash as soon as an breakpoint
in the callback is reached.
What can be done to preven this?
Has anyone success in debugging such code?
