when I launch this on a terminal djtgcfg enum to read my board (Basys 2) it will return this error:
djtgcfg: pthread_mutex_unlock.c:87: __pthread_mutex_unlock_usercnt: Assertio ntype == PTHREAD_MUTEX_ERRORCHECK_NP' failed. Core dump created
What does it mean? I've no ideas. My OS is Ubuntu 15.10 64 bit.
Related
Is there a way of detecting a M1 mac in MATLAB? MATLAB has ismac but that presumably won't differentiate between processor types.
New Answer: Tested on M1 Mac
My impression is that MATLAB is running through Rosetta 2, which means that the result of uname -m is actually x86_64, which does not help guard against calls to Intel targeting mex code.
Instead we'll ask for the kernel version and try to find ARM64
if ismac()
[~,result] = system('uname -v');
is_m1_mac = any(strfind(result,'ARM64'));
else
is_m1_mac = false;
end
Note result above is on my computer : Darwin Kernel Version 21.5.0: Tue Apr 26 21:08:37 PDT 2022; root:xnu-8020.121.3~4/RELEASE_ARM64_T6000
Old Answer: Not correct
To detect the processor one can call to the system command line:
Detect Apple Silicon from command line
Note, this has not been tested on a m1 mac ...
if ismac()
[~,result] = system('uname -m');
is_m1_mac = strcmp(strtrim(result),'arm64');
else
is_m1_mac = false;
end
Note, this would help if you are running an older version of MATLAB, as MATLAB doesn't officially support M1 macs until 2020b update 3 ...
https://www.mathworks.com/matlabcentral/answers/641925-is-matlab-supported-on-apple-silicon-macs
However, it is not clear to me that this would eventually detect execution of MATLAB natively vs via ROSETTA (when a native option actually exists).
Update: from reading others with same error, I'm wondering if this somehow specific to Mac M1. But it's strange the same operations work from the Mac Terminal, just not in VS Code.
Running either lldb target/debug/rust or rust-lldb target/debug/rust from the VS Code Terminal will open the debugger, but running the program (with or without breakpoint at the main function) returns:
error: process exited with status -1 (attach failed ((os/kern) invalid argument))
I'm running on Mac M1. Running the same stuff from Mac Terminal works fine.
From VS Code Terminal:
rust % which lldb
/usr/bin/lldb
rust % which rust-lldb
/Users/me/.cargo/bin/rust-lldb
which is the same as Mac Terminal.
I'm a beginner of HTK (Hidden Markov Model Toolkit).
I just compiled and installed it on my Mac machine (MacOS Sierra).
When I run a HSLab command like:
HSLab no_name
it opens a GUI window properly. But when I click "rec" it crashes with:
ERROR [+6015] StartAudioInput: null audio device
FATAL ERROR - Terminating program HSLab
The HTK version is 3.4.1 (current stable).
Any ideas?
I can produce the same error on my Linux machine (openSUSE Leap 42.2) running Pulseaudio sound manager. The fix for me is to prefix the command with padsp as in:
padsp HSLab no_name
Then the rec button works correctly. I'm not sure the audio recorded is what is required, but that is another issue. No doubt one day we will be able to compile HTK to be PA aware.
Everything going well, building ruby-shoes app on imac. Attempt to dev/run packaged app on my air get illegal instruction.
only happens with latest shoes version (federalas). seems to be ok on policeman
checked the architecture / file type - identical on both machines (e.g. x86_64)
seems to be ./pango-querymodules that causes the first illegal instruction
both machines OSX Yosemite (10.10.3)
attempted to install shoes from scratch and also tried to copy over from working imac version
has anyone seen this? I need to start digging into all files md5, libraries etc, but thought i'd ask the question before i embark
thanks
Output/Data
/Applications/Shoes.app/Contents/MacOS/shoes-launch myapp.rb
/Applications/Shoes.app/Contents/MacOS/shoes-launch: line 8: 57221 Illegal instruction: 4 PANGO_RC_FILE="$APPPATH/pangorc" ./pango-querymodules > pango.modules
/Applications/Shoes.app/Contents/MacOS/shoes-launch: line 9: 57503 Illegal instruction: 4 DYLD_LIBRARY_PATH="$APPPATH" PANGO_RC_FILE="$APPPATH/pangorc" SHOES_RUBY_ARCH="x86_64-darwin14.0" ./shoes-bin "$#"
File type of program with illegal instruction
$ file /Applications/Shoes.app/Contents/MacOS/pango-querymodules
/Applications/Shoes.app/Contents/MacOS/pango-querymodules: Mach-O 64-bit executable x86_64
I wanted to do again to develop in haxe on my MacBook after quite a long time. So I go on haxe.org, download the mac installer and install the latest version of haxe with it.
Then I open the terminal and type haxe, just to encounter this short error message:
Bus Error
Well, did I do something wrong? I'm using OSX 10.4, can it be that the latest version of haxe is not supported on this operating system?
UPDATE:
Looking into the system log, I found out that after the installer was called, the following messages:
Nov 12 18:12:16 my-computer authexec: executing /Volumes/haXe Installer/haXe Installer.app/Contents/MacOS/hxinst-osx
Setting FD_CLOEXEC on all file descriptors
Initializing child but not closing any file descriptors...
Initializing child but not closing any file descriptors...
Nov 12 18:13:25 my-computer crashdump[1655]: haxe crashed
Nov 12 18:13:25 my-computer crashdump[1655]: crash report written to: /Users/myuser/Library/Logs/CrashReporter/haxe.crash.log
Also, investigating the crash log, I got a name for the exception which resulted from the crash:
Exception: EXC_BAD_ACCESS (0x0001)
Codes: KERN_PROTECTION_FAILURE (0x0002) at 0x00000000
Any idea? I'm investigating the problem further.
Bus error means that the program itself is broken (specifically, it means that the program used an unaligned or completely garbage pointer). To find out why, you could try attaching gdb (gdb haxe) and poking around
It is very likely that the installer was built on and targeted for a later version of OS X (either 10.5 or 10.6). You may find more information in your system log (/Applications/Utilities/Console.app). You could ask in the Haxe community or, if you're feeling brave, you could try building your own version from source.