Bug #5727
closedchirp-daily-20180412 EXC_BAD_ACCESS (SIGSEGV) on OSX high sierra
0%
Description
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 Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0x0000000000000006
Exception Note: EXC_CORPSE_NOTIFY
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
Files
Updated by peter håkanson about 6 years ago
- File VHF-config.img VHF-config.img added
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 almost 6 years ago
Chirp-daily 20180512 also affected . See attatched dump
OSX 10.13.4
Updated by peter håkanson almost 6 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 almost 6 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 about 4 years ago
- Target version set to chirp-legacy
- Chirp Version changed from 0.4.0 to daily
- Platform changed from Windows to MacOS
Updated by Bernhard Hailer over 3 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
CableGuide FTDI OEM Cables
RTSystemsCablesAndMavericks
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 over 3 years ago
- Status changed from Feedback to Closed
No more feedback by submitter.