Assertion hit when resolving a break point [#8731]

[LeadAssimilator]

Please see/reopen #8731.

Just because a reported issue might be a problem in mono, does NOT mean the issue should be closed and ignored here. The issue still needs tracked here so everyone that experiences the same problem with xamarin-macios can see it openly and help drive resolution, even if the primary work to fix it is elsewhere. Also, once a fix is provided in mono (if that is where the problem actually lies), then xamarin-macios needs to take the mono update and issue new builds which requires work in xamarin-macios that should reference #8731. Therefore #8731 should be reopened and remain open until mono/mono#19899 is resolved. Thanks.

[LeadAssimilator]

The original issue #8731 still occurs with xamarin-macios 16.4.0.6, but with different line numbers error: * Assertion at /Users/builder/jenkins/workspace/archive-mono/2020-02/ios/release/mono/mini/mini-arm64.c:5447, condition `native_offset % 4 == 0' not met

[LeadAssimilator]

Repro app: XMI8731_M19899.zip

[rolfbjarne]

OK, we'll keep this open until mono/mono#19899 is fixed and we've updated our mono dependency accordingly.

[mlancione]

I have posted the following repro net9.0-ios app to mono/mono#19899

debugger_assert.zip

Debugger Assert:
error: * Assertion at /Users/runner/work/1/s/src/mono/mono/mini/mini-arm64.c:6876, condition `native_offset % 4 == 0' not met

Steps to reproduce:

1. Place a breakpoint at AppDelegate.cs:34
2. Run application with debugger
3. Step-over from breakpoint

Test Environment:
iOS Simulator running on MacOS 14.7 on Apple Silicon
VS Code using .NET MAUI extension or .NET Meteor extension

[mlancione]

It looks like this issue was finally fixed:
dotnet/runtime#110016

I assume we need to wait for a new .NET for iOS update that uses the new mono code to get the fix?

Thanks!

[rolfbjarne]

@mlancione as it stands right now, it looks like the mono fix will be included in the next .NET 10 preview (which will be RC 1). I've asked to get it backported to .NET 9, so it may get backported there as well.

The mono fix will not need any changes or updates to the iOS workload, so I'm closing this issue (once the fix has been released, updating .NET itself to a version with the fix is enough to get it).