segmentation fault when enumerating devices

[jcable]

I got a segfault running SoapySDR::Device:enumerate in code so I installed all packages and ran the command line equivalent and got the same result.

This is with no hardware attached.

SoapySDRUtil --find
######################################################

Soapy SDR -- the SDR abstraction library

######################################################

13:21:53.809712 INFO: api_drivers_init:109 [ DEF] Probing 'libxtrxll_pcie.so.0' low-level library
13:21:53.809941 INFO: api_drivers_init:109 [ DEF] Probing 'libxtrxll_libusb3380.so.0' low-level library
[INFO] [UHD] linux; GNU C++ version 13.2.0; Boost_108300; UHD_4.6.0.0+ds1-5.1ubuntu0.24.04.1
Segmentation fault (core dumped)

ii libsoapysdr-dev:amd64 0.8.1-4build1 amd64 SoapySDR library development files
ii libsoapysdr0.8:amd64 0.8.1-4build1 amd64 software defined radio interface library
ii soapyosmo-common0.8:amd64 0.2.5-8build3 amd64 Use gr-osmosdr drivers with SoapySDR (common files)
ii soapysdr-module-airspy:amd64 0.2.0-4 amd64 Airspy device support for SoapySDR (default version)
ii soapysdr-module-all:amd64 0.8.1-4build1 amd64 All device support for default version of SoapySDR (metapackage)
ii soapysdr-module-audio:amd64 0.1.1-5build2 amd64 Audio device support for SoapySDR (default version)
ii soapysdr-module-bladerf:amd64 0.4.1-5 amd64 bladeRF device support for SoapySDR (default version)
ii soapysdr-module-hackrf:amd64 0.3.4-1 amd64 HackRF device support for SoapySDR (default version)
ii soapysdr-module-lms7:amd64 23.11.0+dfsg-2build2 amd64 Lime Microsystems LMS7 device support for SoapySDR (default version)
ii soapysdr-module-mirisdr:amd64 0.2.5-8build3 amd64 Mirics SDR device support for SoapySDR (default version)
ii soapysdr-module-osmosdr:amd64 0.2.5-8build3 amd64 OsmoSDR device support for SoapySDR (default version)
ii soapysdr-module-redpitaya:amd64 0.1.1-5 amd64 RedPitaya device support for SoapySDR (default version)
ii soapysdr-module-remote:amd64 0.5.2-4 amd64 Use SoapySDR devices over network (default client module)
ii soapysdr-module-rfspace:amd64 0.2.5-8build3 amd64 RFSpace device support for SoapySDR (default version)
ii soapysdr-module-rtlsdr:amd64 0.3.3-1build1 amd64 RTL-SDR device support for SoapySDR (default version)
ii soapysdr-module-uhd:amd64 0.4.1-4build4 amd64 UHD device support for SoapySDR (default version)
ii soapysdr-module-xtrx:amd64 0.0.1+git20191219.98458ce-3build3 amd64 XTRX device support for SoapySDR (default version)
ii soapysdr-tools 0.8.1-4build1 amd64 software defined radio interface library tools
ii soapysdr0.8-module-airspy:amd64 0.2.0-4 amd64 Airspy device support for SoapySDR
ii soapysdr0.8-module-all:amd64 0.8.1-4build1 amd64 All device support for SoapySDR (metapackage)
ii soapysdr0.8-module-audio:amd64 0.1.1-5build2 amd64 Audio device support for SoapySDR
ii soapysdr0.8-module-bladerf:amd64 0.4.1-5 amd64 bladeRF device support for SoapySDR
ii soapysdr0.8-module-hackrf:amd64 0.3.4-1 amd64 HackRF device support for SoapySDR
ii soapysdr0.8-module-lms7:amd64 23.11.0+dfsg-2build2 amd64 Lime Microsystems LMS7 device support for SoapySDR
ii soapysdr0.8-module-mirisdr:amd64 0.2.5-8build3 amd64 Mirics SDR device support for SoapySDR
ii soapysdr0.8-module-osmosdr:amd64 0.2.5-8build3 amd64 OsmoSDR device support for SoapySDR
ii soapysdr0.8-module-redpitaya:amd64 0.1.1-5 amd64 RedPitaya device support for SoapySDR
ii soapysdr0.8-module-remote:amd64 0.5.2-4 amd64 Use SoapySDR devices over network (client module)
ii soapysdr0.8-module-rfspace:amd64 0.2.5-8build3 amd64 RFSpace device support for SoapySDR
ii soapysdr0.8-module-rtlsdr:amd64 0.3.3-1build1 amd64 RTL-SDR device support for SoapySDR
ii soapysdr0.8-module-uhd:amd64 0.4.1-4build4 amd64 UHD device support for SoapySDR
ii soapysdr0.8-module-xtrx:amd64 0.0.1+git20191219.98458ce-3build3 amd64 XTRX device support for SoapySDR

[zuckschwerdt]

That's a lot of modules. Can you isolate the fault to one module? Perhaps binary search by bisecting the modules each round and a/b test.

[jcable]

I got the error in my code when I only had libsoapysdr-dev installed. Then I installed soapysdr-tools and got the same error on the command line. Then I installed other modules to see if there was a missing assumption but the problem remained.

The segfault seems to occur in libusb.

[jcable]

I’ve put together a minimal test which reproduces the problem

https://github.com/Drm-tools/dream/actions/runs/20554614919/job/59037023902

github action which installs libsoapysdr-dev and soapysdr-tools into a clean Ubuntu 24-04 and then runs SoapySDRUtil —find.

It ends with the unix cmd true so the failure must be coming from a SoapySDRUtil crash.

[zuckschwerdt]

Using https://cloud-images.ubuntu.com/noble/20251213/noble-server-cloudimg-amd64.img
and sudo apt-get install libsoapysdr-dev soapysdr-tools
then SoapySDRUtil --find ; echo $? I don't see a crash, just the expected

No devices found!
1

Your test shows the same result. The crash will be somewhere else.

[jcable]

A bit more information. It seems OK on a clean boot. But after someone has remoted in using RDP I get this in dmesg:

[ 1202.701025] SoapySDRUtil[4483]: segfault at 0 ip 0000771a32ac193a sp 0000771a2edfd098 error 4 in libc.so.6[c193a,771a32a28000+188000] likely on CPU 1 (core 1, socket 0)
[ 1202.701036] Code: f3 0f 1e fa 66 0f ef c0 66 0f ef c9 66 0f ef d2 66 0f ef db 48 89 f8 48 89 f9 48 81 e1 ff 0f 00 00 48 81 f9 cf 0f 00 00 77 66 0f 6f 20 66 0f 74 e0 66 0f d7 d4 85 d2 74 04 0f bc c2 c3 48 83
[ 1287.942676] SoapySDRUtil[5062]: segfault at 0 ip 000073cc012c193a sp 000073cbfd5fd098 error 4 in libc.so.6[c193a,73cc01228000+188000] likely on CPU 0 (core 0, socket 0)
[ 1287.942686] Code: f3 0f 1e fa 66 0f ef c0 66 0f ef c9 66 0f ef d2 66 0f ef db 48 89 f8 48 89 f9 48 81 e1 ff 0f 00 00 48 81 f9 cf 0f 00 00 77 66 0f 6f 20 66 0f 74 e0 66 0f d7 d4 85 d2 74 04 0f bc c2 c3 48 83

[zuckschwerdt]

RDP is unlikely to interact with SoapySDR I'd say. Is there some hardware added / used / discovered, perhaps using USB, that might trigger this crash in a module?
Can you remove all modules (something like mv /usr/lib/SoapySDR/modules0.8-3 /usr/lib/SoapySDR/modules0.8-3_bak) and test if the crash goes away?