I spent quite a while troubleshooting a bug in which RX would mysteriously not restart, if you did a hackrf-stop-rx followed by another hackrf-start-rx. The problem actually was not in my code, but due to some old libhackrf bugs that had not been patched in the old Debian 9 version of libhackrf which I am using.
This is a serious enough annoyance that you won’t want to be using HackRF Shell with the unpatched version. So, I added instructions to my git repo (debian9-libhackrf-patch directory, see commit 346c50e) on how to get a patched version of the Debian 9 packages. I think that the Debian 10 library version is actually not new enough to avoid all the bugs, either, so the info I have provided might be of value to Debian 10 users as well.
I would like to switch my home system from Debian to Gnu Guix, and use Guix package management for development, but I’m not sure how soon that will happen.
git clone git://git.librehacker.com/pub/git/hackrf-rkt.git
The Libre Hacker 
Good find! Its tough when you scour your code for a problem, only to find the real issue is something outside of your code.
LikeLike
What does ‘shell’ and ‘patch’ mean in terms of code?
LikeLike
Hi Lars, “HackRF Shell” is the program I wrote to control the HackRF from an interpreter prompt. “Patch” means to make a small change to some code to fix something or to add a feature, usually when you don’t want to upgrade to a newer version.
I should have you come over sometime this week and I can show you some of this stuff on my computer.
LikeLike