Github messages for voidlinux
 help / color / mirror / Atom feed
From: paper42 <paper42@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [ISSUE] [CLOSED] seg fault using aispy + SoapySDR
Date: Tue, 22 Mar 2022 19:29:50 +0100	[thread overview]
Message-ID: <20220322182950.AA45bdkpn5uF9sZ5MY2LDyFCFaJfbGuUX3Ye6d0gNWI@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-35650@inbox.vuxu.org>

[-- Attachment #1: Type: text/plain, Size: 1822 bytes --]

Closed issue by neoklis on void-packages repository

https://github.com/void-linux/void-packages/issues/35650

Description:
<!-- Don't request update of package. We have a script for that. https://alpha.de.repo.voidlinux.org/void-updates/void-updates.txt . However, a quality pull request may help. -->
### System
AMD64 (Compulab FitPC4 computer)
* package:  airspy-1.0.10_1

### Expected behavior
Should work with Airspy SDR
### Actual behavior
Segmentation fault
### Steps to reproduce the behavior
Problem started recently, possibly after and update of Void. When running any application
that uses an Airspy SDR in conjunction with SoapySDR, SoapyAirspy  and libairspy then a seg fault occurs:

Thread 1 "sdrx" received signal SIGSEGV, Segmentation fault.
0x0000000000d2f520 in ?? ()
(gdb) bt
#0  0x0000000000d2f520 in ?? ()
#1  0x00007ffff5e32c88 in ?? () from /usr/lib/libusb-1.0.so.0
#2  0x00007ffff5e334ba in ?? () from /usr/lib/libusb-1.0.so.0
#3  0x00007ffff5e37bb1 in libusb_free_transfer () from /usr/lib/libusb-1.0.so.0
#4  0x00007ffff7349d89 in ?? () from /usr/lib/libairspy.so.0
#5  0x00007ffff734a599 in airspy_close () from /usr/lib/libairspy.so.0
#6  0x000000000041bf28 in Airspy_Get_Samplerates ()
#7  0x000000000040e5f9 in Append_Sample_Rates ()
#8  0x000000000040adef in Device_Combobox_Changed ()

"sdrx" is an SDR receiver client I wrote myself. Its been working well for a long time. The fault occurs with another app I wrote, "glrpt", which was also working well for some years.

The fault doesn't occur when using the same apps with RTL-SDR devices so it seems to be an issue with airspy libs. I have no clear indications that my apps are to blame but I see that both SoapySDR and airspy libs are outdated versions. 

My thanks in advance

Neoklis

www.5b4az.org

      parent reply	other threads:[~2022-03-22 18:29 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-16  9:37 [ISSUE] " neoklis
2022-02-17  5:18 ` neoklis
2022-02-17 12:28 ` tibequadorian
2022-02-17 13:14 ` neoklis
2022-02-19 19:48 ` paper42
2022-02-19 19:48 ` paper42
2022-02-20  5:07 ` neoklis
2022-03-22 18:29 ` paper42 [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20220322182950.AA45bdkpn5uF9sZ5MY2LDyFCFaJfbGuUX3Ye6d0gNWI@z \
    --to=paper42@users.noreply.github.com \
    --cc=ml@inbox.vuxu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).