I’m seeing cases in which breakpoints are never being hit, in Job code which is definitely running. I’ve run into multiple cases of this over the past week (still with Entities 0.1.1).
Are there any known cases which could cause this? Have you seen the same?
Thank you for any help. This is preventing us from tracking down some bugs.
It happens to me when Burst compilation is enabled, when I disable Burst breakpoints are being hit.
Thank you! I am using Burst. Do you know if this is expected/intended behavior from the Burst team?
Expected. Because bursted job compiled by JIT compiler at runtime and currently it’s not your C# code anymore. If you want debug specific job, comment burst for this job.
With the new JobComponentSystem Entities.ForEach() breakpoints are not being hit for me inside the lambda (<>c__DisplayClass_OnUpdate_LambdaJob0.OriginalLambdaBody()) in Visual Studio 2017 even with Burst disabled in Unity Editor. Interestingly they are being hit in Rider 2019.2.3. Is it some limitation of Visual Studio?
I’ve found problems with break points inside jobs sometimes not being hit in Visual Studio under MacOs (of course with burst turned off).
On Windows I had no problems.