It did, yes. I’ve seen issues with breakpoints too that I’m due to investigate next week, but Carlo could not reproduce them, so we assumed it was a localized problem for me, but I guess it could be Windows vs Mac. I’ll try to give this top priority on Monday.
Didn’t retest yet (next on my list), but should be fixed oin latest. you don’t need new Fire, just external compiler, as it turns out the issue wasn’t the debugger, but that the compiler stopped generating Portable PDB debug symbols when running on Mono, at some stage.
Fixed, but I’m not closing the issue yet because the fix is more an error-proofing around what really goes wrong (on Mac only) and I still wanna have the root cause investigated. But it’ll work in tomorrow’s build.
I attach to the issue with my problem. In the latest Fire I create new console app project and run but get error :
~> The process failed to start with the following error: System.ArgumentNullException: Value cannot be null.
~> Parameter name: path1
~> at System.IO.Path.Combine (System.String path1, System.String path2) [0x00003] in <2978dc2b6099412f90677716ee4026f5>:0
~> at RemObjects.Oxygene.CoreDebugEngine.MIDebugEngine.Start () [0x000d0] in <5c7a7f214afb4935b35f9e32af1e2fb0>:0
~> at (wrapper native-to-managed) RemObjects.Oxygene.CoreDebugEngine.DebugEngine.Start(RemObjects.Oxygene.CoreDebugEngine.DebugEngine,System.Exception&)