macOS Sonoma Crash

[overbog]

Crashes at startup:

Crashed Thread: 4 Dispatch queue: CA DispatchGroup

Exception Type: EXC_BAD_ACCESS (SIGSEGV) Exception Codes: KERN_INVALID_ADDRESS at 0x000000000000024a Exception Codes: 0x0000000000000001, 0x000000000000024a

Termination Reason: Namespace SIGNAL, Code 11 Segmentation fault: 11 Terminating Process: exc handler [17843]

[jmohin]

Same for me:

Crashed Thread: 14 Dispatch queue: CA DispatchGroup

Exception Type: EXC_BAD_ACCESS (SIGSEGV) Exception Codes: KERN_INVALID_ADDRESS at 0x000000000000024a Exception Codes: 0x0000000000000001, 0x000000000000024a

Termination Reason: Namespace SIGNAL, Code 11 Segmentation fault: 11 Terminating Process: exc handler [2467]

VM Region Info: 0x24a is not in any region. Bytes before following region: 140737488227766 REGION TYPE START - END [ VSIZE] PRT/MAX SHRMOD REGION DETAIL UNUSED SPACE AT START --->
shared memory 7ffffffe1000-7ffffffe2000 [ 4K] r-x/r-x SM=SHM

[daBee]

Mac Mini M1, Sonoma.

PC register does not match crashing frame (0x0 vs 0x100D2D2D0)

Crashed Thread: 35 Dispatch queue: CA DispatchGroup

Exception Type: EXC_BAD_ACCESS (SIGSEGV) Exception Codes: KERN_INVALID_ADDRESS at 0x000000000000024a Exception Codes: 0x0000000000000001, 0x000000000000024a

Termination Reason: Namespace SIGNAL, Code 11 Segmentation fault: 11 Terminating Process: exc handler [64585]

VM Region Info: 0x24a is not in any region. Bytes before following region: 140722850856374 REGION TYPE START - END [ VSIZE] PRT/MAX SHRMOD REGION DETAIL UNUSED SPACE AT START --->
mapped file 7ffc97898000-7ffcbcfb8000 [599.1M] r-x/r-x SM=COW ...t_id=120a9d93

Error Formulating Crash Report: PC register does not match crashing frame (0x0 vs 0x100D2D2D0)

[sidewinder666]

2021 Macbook Pro M1, upgraded to Sonoma and now CubicSDR crashes at startup with similar message the others have already posted:

Notes: PC register does not match crashing frame (0x0 vs 0x100E3E2D0)

Crashed Thread: 15 Dispatch queue: CA DispatchGroup

Exception Type: EXC_BAD_ACCESS (SIGSEGV) Exception Codes: KERN_INVALID_ADDRESS at 0x0000000000000008 Exception Codes: 0x0000000000000001, 0x0000000000000008

Termination Reason: Namespace SIGNAL, Code 11 Segmentation fault: 11 Terminating Process: exc handler [13403]

[lagomorph]

same on 2019 MBP upgraded to Sonoma

[dtanonis]

Same here 2020 MBP after Sonoma upgrade, reopen doesn't take

Process: CubicSDR [1801] Path: /Applications/CubicSDR.app/Contents/MacOS/CubicSDR Identifier: com.cubicproductions.cubicsdr Version: 0.2.4 (0.2.4) Code Type: X86-64 (Native) Parent Process: launchd [1] User ID: 501

Date/Time: 2023-10-15 10:39:53.9834 -0700 OS Version: macOS 14.0 (23A344) Report Version: 12 Bridge OS Version: 8.0 (21P365) Anonymous UUID: C4FFCAF1-2037-F15C-C919-00C898E99893

Sleep/Wake UUID: 13F80E1B-2976-4E1E-87EC-1DD6E5E92760

Time Awake Since Boot: 15000 seconds Time Since Wake: 1548 seconds

System Integrity Protection: enabled

Crashed Thread: 3 Dispatch queue: CA DispatchGroup

Exception Type: EXC_BAD_ACCESS (SIGSEGV) Exception Codes: KERN_INVALID_ADDRESS at 0x000000000000024a Exception Codes: 0x0000000000000001, 0x000000000000024a

Termination Reason: Namespace SIGNAL, Code 11 Segmentation fault: 11 Terminating Process: exc handler [1801]

[rhaguiuda]

Same on iMac Intel i7

[timmattison]

Tried compiling it from scratch this morning and it works again for me. You'll need all of the dependencies installed first but usually I do this for a new C/C++ project on MacOS:

git clone whatever...
cd whatever
mkdir build
cd build
cmake ..

If that doesn't report any errors then just run make. If it does report an error like Liquid DSP is missing I just do:

brew search liquid

And see if there's a package for it. If there is I install it and try again. And that's how I got CubicSDR running on my machine. It's awful, but it works.

[cixio]

Since the current unreleased version seems to be without this bug (and I can't manage to build it myself), would it make sense to create a new release? After all, the old one is already over 1.5 years old. @cjcliffe

[sidewinder666]

Agreed with cixio. I can't seem to get that built, either. A new version release would be very much appreciated.

[bobbyl140]

+1 on OP, will try building

[bobbyl140]

Never mind, I can't figure out these dependencies.

[bobbyl140]

For any still interested, 0.2.3 opens right away for me on Sonoma. Try that one!

[sidewinder666]

And I'll confirm that, v0.2.3 works fine on Sonoma (M1 Macbook Pro). That begs the question "What broke?" in 0.2.4 and 0.2.5.

[bobbyl140]

Without looking at any of the code, my first guess would be dependency updates, but take that with a grain of salt.

[cixio]

For any still interested, 0.2.3 opens right away for me on Sonoma. Try that one!

Thanks, works also on my 2021 14'' M1 Pro

And I'll confirm that, v0.2.3 works fine on Sonoma (M1 Macbook Pro). That begs the question "What broke?" in 0.2.4 and 0.2.5.

The actual code works also great (if you build it yourself), but I couldn't get the soapy modules running as I dont understand the build manual.

[vk2tty]

This covered my attempt:

brew install cmake liquid-dsp wxwidgets

… but I'm not sure what I already had installed that might have helped. Anyhow, got b959ff compiled and working on macOS "Sonoma" 14.2 (23C64).

[radito]

Just finished building v0.2.8 for Apple ARM, if somebody want to give it a try Running some test right now on m1 sonoma 14.3.1 and seems to works fine

https://github.com/radito/CubicSDR/releases/tag/0.2.8

[vk2tty]

"CubicSDR.app" can't be opened because Apple cannot check it for malicious software. This software needs to be updated. Contact the developer for more information.

[radito]

"CubicSDR.app" can't be opened because Apple cannot check it for malicious software. This software needs to be updated. Contact the developer for more information.

Can you try dragging the app out from .dmg to another folder, and open it by right clicking it. Probably signing issue since i don't have valid signing certificate

Then click open

[sidewinder666]

Radito, while that did work to open the app without a crash, the following was shown once it opened:

[radito]

Radito, while that did work to open the app without a crash, the following was shown once it opened:

Okay thanks, i'm taking a look into it.

[mg1011]

Radito, while that did work to open the app without a crash, the following was shown once it opened:

Okay thanks, i'm taking a look into it.

Can confirm using RSP1A on Mac M1 Pro with latest OS. Also have RTL-SDR V4 and HF+ Discovery to test with if needed.

[radito]

CubicSDR build with added SoapySDR Bundle config https://github.com/radito/CubicSDR/releases/tag/0.2.8-2

If there's a macOS error ignore it, just right click -> open (because it's not signed with apple developer, it uses adhoc sign)

Feedback would be useful to validate if the issue is fixed.

[sidewinder666]

Perhaps it's "just me" but I get the same symptoms as before. Opening it shows this:

2021 16" Macbook Pro M1, Sonoma 14.4

[radito]

@sidewinder666

can you try

brew install soapysdr soapyrtlsdr

see if that helps ?

[sidewinder666]

Thanks for the suggestion, I had hoped it would help, but... (I also hadn't run Homebrew in ages, that took a long time to get done. Brew updated two pages worth of... things... and I had to first install command-line tools to get something else updated. Thankfully, it all seemed to work. ) The two extensions installed without error, however when I open the app I get the exact same error. I can dismiss the error but then no devices show up at all.

[radito]

Sorry, after digging more in the build system just figure it out my soapy sdr isn't in this build directory, because it's referenced using homebrew SET(SOAPY_SDR_MOD_PATH "${CMAKE_INSTALL_PREFIX}/lib/SoapySDR/modules${SOAPY_SDR_ABI_VERSION}")

Need some adjustment, hope it will be fixed.

[sidewinder666]

Umm, apologies, but... are you asking me to run that command in shell, or just thinking out loud what you're going to do to make another build?

[radito]

No, you're fine. i'm just informing for another build, but gonna test on my machine first.

Because rn im using soapySDR from homebrew and it's referenced in another directory. maybe that's what's causing the problem.

[radito]

yeah, i think that's what's causing the problem.

Working on a fix rn.