Arduino Setup Not Working, Support Packages Cannot be Verified

I am trying to install MATLAB libraries for Arduino. I try to verify my support package add-ons I get this error message

May 29, 2023 9:48:22 PM com.mathworks.hwservices.logging
INFO: Loading configuration...
Initializing packages...
Preparing boards...
Verifying...
/Users/chris/Documents/MATLAB/SupportPackages/R2019a/3P.instrset/arduinoide.instrset/Arduino.app/Contents/Java/arduino-builder -dump-prefs -logger=machine -hardware /Users/chris/Documents/MATLAB/SupportPackages/R2019a/3P.instrset/arduinoide.instrset/Arduino.app/Contents/Java/hardware -hardware /Users/chris/Documents/MATLAB/SupportPackages/R2019a/3P.instrset/arduinoide.instrset/idepkgs/packages -tools /Users/chris/Documents/MATLAB/SupportPackages/R2019a/3P.instrset/arduinoide.instrset/Arduino.app/Contents/Java/tools-builder -tools /Users/chris/Documents/MATLAB/SupportPackages/R2019a/3P.instrset/arduinoide.instrset/Arduino.app/Contents/Java/hardware/tools/avr -tools /Users/chris/Documents/MATLAB/SupportPackages/R2019a/3P.instrset/arduinoide.instrset/idepkgs/packages -built-in-libraries /Users/chris/Documents/MATLAB/SupportPackages/R2019a/3P.instrset/arduinoide.instrset/Arduino.app/Contents/Java/libraries -libraries /Users/chris/Documents/Arduino/libraries -fqbn=arduino:samd:mkr1000 -vid-pid=0X2341_0X804E -ide-version=10801 -build-path /private/var/folders/1v/2xqmdtwd20l9lsvc26n139t80000gn/T/ArduinoServer/MW -warnings=null -prefs=build.path=/private/var/folders/1v/2xqmdtwd20l9lsvc26n139t80000gn/T/ArduinoServer/MW -prefs=build.warn_data_percentage=75 -prefs=runtime.tools.arduinoOTA.path=/Users/chris/Documents/MATLAB/SupportPackages/R2019a/3P.instrset/arduinoide.instrset/idepkgs/packages/arduino/tools/arduinoOTA/1.2.0 -prefs=runtime.tools.arm-none-eabi-gcc.path=/Users/chris/Documents/MATLAB/SupportPackages/R2019a/3P.instrset/arduinoide.instrset/idepkgs/packages/arduino/tools/arm-none-eabi-gcc/4.8.3-2014q1 -prefs=runtime.tools.bossac.path=/Users/chris/Documents/MATLAB/SupportPackages/R2019a/3P.instrset/arduinoide.instrset/idepkgs/packages/arduino/tools/bossac/1.7.0 -prefs=runtime.tools.CMSIS.path=/Users/chris/Documents/MATLAB/SupportPackages/R2019a/3P.instrset/arduinoide.instrset/idepkgs/packages/arduino/tools/CMSIS/4.5.0 -prefs=runtime.tools.openocd.path=/Users/chris/Documents/MATLAB/SupportPackages/R2019a/3P.instrset/arduinoide.instrset/idepkgs/packages/arduino/tools/openocd/0.9.0-arduino6-static -prefs=runtime.tools.CMSIS-Atmel.path=/Users/chris/Documents/MATLAB/SupportPackages/R2019a/3P.instrset/arduinoide.instrset/idepkgs/packages/arduino/tools/CMSIS-Atmel/1.1.0 -verbose /private/var/folders/1v/2xqmdtwd20l9lsvc26n139t80000gn/T/ArduinoServer/ArduinoServer.ino
/Users/chris/Documents/MATLAB/SupportPackages/R2019a/3P.instrset/arduinoide.instrset/Arduino.app/Contents/Java/arduino-builder returned 139

I understand that the key error lies in the last bit "returned 139"

Upon verification of the setup and test of the Arduino Connection, the Build status fails:

I have tried to reinstall the third-party files.

Keep in mind, this is all happening in Mac, as this is my only option currently.

Any help would be greatly appreciated.

This is my first question, so any tips on how to make future questions better would be greatly appreciated as well.

[Walter Roberson]

error 139 is potentially SIGSEGV, which is an error generated when a program tries to access memory it does not own. I think it can also happen if a program attempts to read from or write to memory address 0

[Christian]

Ah ok. Does this have anything to do with me running MATLAB in Admin mode? I neglected to do that.

I just tried two solutions to run MATLAB with admin privileges using terminal and neither one works. How would I go about giving MATLAB and Arduino access to the memory they need?

[Walter Roberson]

There are a small number of typical causes for this kind of problem:

• program bug, code attempts to read from or write to NULL pointer for random buggy reason
• program bug, code attempts to read from or write to NULL pointer because it failed to check whether memory allocation was successful
• DLL is missing, program attempts to call library function; this situation would more likely get reported by the linker, but is possible with SIGSEGV in some cases involving dynamic linking
• DLL that was found is the wrong version compared to what the program was created with; this situation should get reported by the linker, but that does not always happen

The case where the wrong DLL is found is especially common with Linux, especially in the situation where a program that was linked with one DLL version invokes a program that was linked with a different DLL version; the linker might hand the second program the DLL associated with the first program. The linking mechanisms for dealing with different DLL versions started by the same process are not always robust.

As I watch other posts, it looks like DLL version conflict often involved libC.so.6 . Sometimes it turns out to be necessary to rename or delete libC.so.6 that is provided with MATLAB so that a different process can get to the system-provided libC.so . (I would not recommend outright deleting it before testing... moving it aside maybe.)

[Christian]

I tried searching MATLAB for it and as far as I'm aware, this file does not exist in my Mac.

[Walter Roberson]

Sorry, for some reason I misread and thought you were using Linux.