Tutorial:Troubleshooting Debug on OSX ARM64 - Revision history

Imbion: Imbion moved page Troubleshooting Debug on OSX ARM64 to Tutorial:Troubleshooting Debug on OSX ARM64

2025-10-16T16:36:15Z

Imbion moved page Troubleshooting Debug on OSX ARM64 to Tutorial:Troubleshooting Debug on OSX ARM64

← Older revision	Revision as of 16:36, 16 October 2025
(No difference)

IDK at 19:38, 11 November 2024

2024-11-11T19:38:49Z

← Older revision		Revision as of 19:38, 11 November 2024
Line 60:		Line 60:
	* Plan B was to look into configuration to see if anything could be set right there.		* Plan B was to look into configuration to see if anything could be set right there.
	* Plan C will be an attempt to attach a debugger to the x64 build that does work, and come up with some patch solution on that.		* Plan C will be an attempt to attach a debugger to the x64 build that does work, and come up with some patch solution on that.
	* Plan D is to do it all the hard way and build PMDO with arm64 skiasharp off an example avalonia project plus [[~~https://wiki.pmdo.pmdcollab.org/~~Upgrading_FNA_Dependencies\|Xcode building fnalibs]] plus additional building for [[~~https://wiki.pmdo.pmdcollab.org/~~Upgrading_Lua_Debug\|lualibs and core.so]]		* Plan D is to do it all the hard way and build PMDO with arm64 skiasharp off an example avalonia project plus [[Upgrading_FNA_Dependencies\|Xcode building fnalibs]] plus additional building for [[Upgrading_Lua_Debug\|lualibs and core.so]]



	[[Category: Troubleshooting]]		[[Category: Troubleshooting]]

IDK: reformatting and links

2024-11-11T19:38:02Z

reformatting and links

← Older revision		Revision as of 19:38, 11 November 2024
Line 3:		Line 3:
	However, building and debugging PMDO becomes confusing, as the build toolchain and the IDE may try to use the arm64 version instead of x64. It may build the arm64 version, or debug an x64 build as if it were arm64. Additionally, arm64 libraries are missing and thus cannot be run (at least not without building every dependency for arm64).		However, building and debugging PMDO becomes confusing, as the build toolchain and the IDE may try to use the arm64 version instead of x64. It may build the arm64 version, or debug an x64 build as if it were arm64. Additionally, arm64 libraries are missing and thus cannot be run (at least not without building every dependency for arm64).

	This page goes over the troubleshooting process for getting PMDO to debug on OSX-ARM64. It is currently unresolved.		This page goes over the troubleshooting process for getting PMDO to debug on OSX-ARM64 using Rider. It is currently unresolved.

	~~== Command Line ==~~

	* <code>dotnet build</code>: Fails. It builds out to bin/Debug/net8.0. Complains about libskia.dylib and requires it to be arm64. Ran using ./PMDC		== Sanity Checks ==
	* <code>dotnet build -c Debug -r osx-x64</code>: Successful. It builds out to bin/Debug/net8.0/osx-x64 but does not copy fnalibs. Once they are copied manually, running ./PMDC -dev -asset ../../../../../DumpAsset/ succeeds.


	~~== VS Code ==~~




	~~== Rider ==~~

	=== Sanity Checks ===

	These steps were taken to ensure the setup was correct.		These steps were taken to ensure the setup was correct.

	==== Other Projects ====		=== Other Projects ===

	Attempting to debug on other projects using Rider worked.		Attempting to debug on other projects using Rider worked.

	==== Clearing Rider Cache ====		=== Clearing Rider Cache ===

	File -> Invalidate Cache -> Choose all		File -> Invalidate Cache -> Choose all
Line 32:		Line 20:
	This did not resolve the issue.		This did not resolve the issue.

	==== Clearing Nuget Cache ====		=== Clearing Nuget Cache ===

	Delete <code>~/.nuget</code> to remove all nuget packages so that they'll be redownloaded cleanly on next build.		Delete <code>~/.nuget</code> to remove all nuget packages so that they'll be redownloaded cleanly on next build.
Line 40:		Line 28:
	This did not resolve the issue.		This did not resolve the issue.

	==== Clean Clone from Repository ====		=== Clean Clone from Repository ===

	We are trying the basic Example program that contains the bare minimum in dependencies.		We are trying the basic Example program that contains the bare minimum in dependencies.
Line 50:		Line 38:

	=== Factors to Consider ===		=== Factors to Consider ===

	~~DotNet installations: Do we have more than one NetCore installation?~~

	A:


	We have two runtimes of dotnet: <code>/usr/local/share/dotnet/x64/dotnet</code> and <code>/usr/local/share/dotnet/dotnet</code>. Which runtime do we use in Rider?		We have two runtimes of dotnet: <code>/usr/local/share/dotnet/x64/dotnet</code> and <code>/usr/local/share/dotnet/dotnet</code>. Which runtime do we use in Rider?

	A:


	What are the possible configurations when building/debugging?		What are the possible configurations when building/debugging?

	A:


Line 82:		Line 60:
	* Plan B was to look into configuration to see if anything could be set right there.		* Plan B was to look into configuration to see if anything could be set right there.
	* Plan C will be an attempt to attach a debugger to the x64 build that does work, and come up with some patch solution on that.		* Plan C will be an attempt to attach a debugger to the x64 build that does work, and come up with some patch solution on that.
	* Plan D is to do it all the hard way and build PMDO with arm64 skiasharp off an example avalonia project plus Xcode building fnalibs plus additional building for lualibs and core.so		* Plan D is to do it all the hard way and build PMDO with arm64 skiasharp off an example avalonia project plus [[https://wiki.pmdo.pmdcollab.org/Upgrading_FNA_Dependencies\|Xcode building fnalibs]] plus additional building for [[https://wiki.pmdo.pmdcollab.org/Upgrading_Lua_Debug\|lualibs and core.so]]



	[[Category: Troubleshooting]]		[[Category: Troubleshooting]]

IDK at 02:13, 9 November 2024

2024-11-09T02:13:47Z

← Older revision		Revision as of 02:13, 9 November 2024
Line 7:		Line 7:
	== Command Line ==		== Command Line ==

	* dotnet build: Fails. It builds out to bin/Debug/net8.0. Complains about libskia.dylib and requires it to be arm64. Ran using ./PMDC		* <code>dotnet build</code>: Fails. It builds out to bin/Debug/net8.0. Complains about libskia.dylib and requires it to be arm64. Ran using ./PMDC
	* dotnet build -c Debug -r osx-x64: Successful. It builds out to bin/Debug/net8.0/osx-x64 but does not copy fnalibs. Once they are copied manually, running ./PMDC -dev -asset ../../../../../DumpAsset/ succeeds.		* <code>dotnet build -c Debug -r osx-x64</code>: Successful. It builds out to bin/Debug/net8.0/osx-x64 but does not copy fnalibs. Once they are copied manually, running ./PMDC -dev -asset ../../../../../DumpAsset/ succeeds.

IDK: dotnet build command line

2024-11-09T00:17:01Z

dotnet build command line

← Older revision		Revision as of 00:17, 9 November 2024
Line 5:		Line 5:
	This page goes over the troubleshooting process for getting PMDO to debug on OSX-ARM64. It is currently unresolved.		This page goes over the troubleshooting process for getting PMDO to debug on OSX-ARM64. It is currently unresolved.

	= VS Code =		== Command Line ==

			* dotnet build: Fails. It builds out to bin/Debug/net8.0. Complains about libskia.dylib and requires it to be arm64. Ran using ./PMDC
			* dotnet build -c Debug -r osx-x64: Successful. It builds out to bin/Debug/net8.0/osx-x64 but does not copy fnalibs. Once they are copied manually, running ./PMDC -dev -asset ../../../../../DumpAsset/ succeeds.


			== VS Code ==


Line 66:		Line 72:
	These are the results you get when you perform the following actions with a wiped bin/obj:		These are the results you get when you perform the following actions with a wiped bin/obj:
	* dotnet build: Fails. It builds out to bin/Debug/net8.0. Complains about libskia.dylib and requires it to be arm64. Ran using ./PMDC		* dotnet build: Fails. It builds out to bin/Debug/net8.0. Complains about libskia.dylib and requires it to be arm64. Ran using ./PMDC
	* dotnet build -c Debug -r osx-x64: Successful. It builds out to bin/Debug/net8.0/osx-x64 but does not copy fnalibs. Once ~~done~~ manually, running ./PMDC -dev -asset ../../../../../DumpAsset/ succeeds.		* dotnet build -c Debug -r osx-x64: Successful. It builds out to bin/Debug/net8.0/osx-x64 but does not copy fnalibs. Once they are copied manually, running ./PMDC -dev -asset ../../../../../DumpAsset/ succeeds.
	* Debugging in Rider with PMDC configured to Any CPU: Exact same result as dotnet build.		* Debugging in Rider with PMDC configured to Any CPU: Exact same result as dotnet build.
	* Debugging in Rider with PMDC configured to x64: Fails. It builds out to bin/Debug/net8.0. Complains with System.IO.FileLoadException: Could not load file or assembly 'PMDC'. This error also shows up if ran using ./PMDC		* Debugging in Rider with PMDC configured to x64: Fails. It builds out to bin/Debug/net8.0. Complains with System.IO.FileLoadException: Could not load file or assembly 'PMDC'. This error also shows up if ran using ./PMDC

IDK: Rider debugging

2024-11-08T23:35:54Z

Rider debugging

@@ Line 5: / Line 5: @@
 This page goes over the troubleshooting process for getting PMDO to debug on OSX-ARM64.  It is currently unresolved.
-== VS Code ==
+= VS Code =
@@ Line 12: / Line 12: @@
 == Rider ==
 [[Category: Troubleshooting]]

IDK: first post

2024-11-08T22:17:06Z

first post

New page

Starting with apple M1, all mac OSes run on ARM64. Existing x64 programs can still work on it thanks to rosetta, and indeed published versions of PMDO for oxs-x64 work just fine.

However, building and debugging PMDO becomes confusing, as the build toolchain and the IDE may try to use the arm64 version instead of x64. It may build the arm64 version, or debug an x64 build as if it were arm64. Additionally, arm64 libraries are missing and thus cannot be run (at least not without building every dependency for arm64).

This page goes over the troubleshooting process for getting PMDO to debug on OSX-ARM64. It is currently unresolved.

== VS Code ==

== Rider ==

[[Category: Troubleshooting]]