Bug #5727

chirp-daily-20180412 EXC_BAD_ACCESS (SIGSEGV) on OSX high sierra

Added by peter håkanson over 4 years ago. Updated about 2 years ago.

Status:Closed Start date:04/15/2018
Priority:Normal Due date:
Assignee:- % Done:


Target version:chirp-daily
Chirp Version:daily Platform:MacOS
Model affected:Baofeng UV-5R


This has been the case on 20180325 and 20180331

OSX problem details shows :
System Integrity Protection: enabled

Crashed Thread: 0 Dispatch queue: com.apple.main-thread

Exception Codes: KERN_INVALID_ADDRESS at 0x0000000000000006

The full debug is at ftp://ftp.manet.nu/pub/chirp/chirp-20180412-err.txt

I'm running
System Version: macOS 10.13.4 (17E199)
Kernel Version: Darwin 17.5.0
Boot Volume: Macintosh HD
Boot Mode: Normal
User Name: xxxxx
Secure Virtual Memory: Enabled
System Integrity Protection: Enabled
Time since boot: 3 days 3:44

VHF-config.img - Config for baofeng uv-5r (6.3 kB) peter håkanson, 04/15/2018 11:19 pm

crash (72.8 kB) peter håkanson, 05/14/2018 10:57 am


Updated by peter håkanson over 4 years ago

Platform is OSX, sorry about the wrong type in the "platform" field.
The crash occurs right after cloning a radio ( baofeng uv-5r) , the radio has been correctly
programmed and is rebooting itself. Then chirp dies. Radio functions as expected after programming.
Channel list attatched

Updated by peter håkanson over 4 years ago

Chirp-daily 20180512 also affected . See attatched dump
OSX 10.13.4

Updated by peter håkanson over 4 years ago

chirp-daily-20180623 has same problem. Chirp dies after programming a radion, but programming is done ok. Still an annoying problem. OSX 10.13.5

Updated by peter håkanson over 4 years ago

chirp-daily-20180707 has same problem, 3 of 4 uploads end in chirp crash
Still running osx high sierra 10.13.5, no other problems with this computer

Updated by Bernhard Hailer over 2 years ago

  • Target version set to chirp-daily
  • Chirp Version changed from 0.4.0 to daily
  • Platform changed from Windows to MacOS

Updated by Bernhard Hailer about 2 years ago

  • Status changed from New to Feedback
  • Model affected changed from (All models) to Baofeng UV-5R

I'm not a Mac user; but it seems to me that there's something specific to your setup which causes the trouble. Perhaps you're using a damaged USB cable driver?

Please review these files:
CableGuide FTDI OEM Cables
If there's no solution to be found in any of them, please read: How To Report Issues and provide a debug log. Thank you!
MacOS notes: this OS is apparently very picky about USB to Serial cables. From what I heard, only (genuine) FTDI-based cables can be made work.
You must have the KK7DS Python runtime for Mac OSX installed.
Also see MacOS Tips!
Bluetooth notes: connections often suffer from timing issues, please try a cable instead.

Please let us know how it goes.

Updated by Bernhard Hailer about 2 years ago

  • Status changed from Feedback to Closed

No more feedback by submitter.

Also available in: Atom PDF