Jump to content
  • 0

Segmentation fault on Ubuntu 16.04.4 LTS


Branden Allen

Question

I am having a similar issue when running as a normal user under Ubuntu 16.04.4 LTS and have installed the following packages per the standard instructions for running the Analog Discovery 2 device.

ii  digilent.adept.runtime                               2.17.1                                      amd64        Digilent Adept Runtime
ii  digilent.waveforms                                   3.7.5                                         amd64        Digilent WaveForms

Currently I am only able to run waveforms under "sudo" and not as a standard user.  As a standard user executing

env LD_LIBRARY_PATH=/usr/lib/digilent/waveforms/qtlibs gdb /usr/lib/digilent/waveforms/waveforms

Thread 10 "waveforms" received signal SIGSEGV, Segmentation fault

0x00007fffecce2fc6 in libusb_close () from /lib/x86_64-linux-gnu/libusb-1.0.so.0

The Full Backtrace is as follows

#0  0x00007fffecce2fc6 in libusb_close () from /lib/x86_64-linux-gnu/libusb-1.0.so.0
#1  0x00007fff375e492d in CloseDevice () from /usr/lib64/digilent/adept/libftd2xx.so
#2  0x00007fff375e5c91 in OpenDevice () from /usr/lib64/digilent/adept/libftd2xx.so
#3  0x00007fff375e61ed in FTCommonOpen () from /usr/lib64/digilent/adept/libftd2xx.so
#4  0x00007fff375e633e in FT_OpenEx () from /usr/lib64/digilent/adept/libftd2xx.so
#5  0x00007fffefd55cae in ?? () from /usr/lib64/digilent/adept/libdpcomm.so.2
#6  0x00007fffefd501b3 in ?? () from /usr/lib64/digilent/adept/libdpcomm.so.2
#7  0x00007fffefd4c6f8 in ?? () from /usr/lib64/digilent/adept/libdpcomm.so.2
#8  0x00007fffefd4a3d6 in ?? () from /usr/lib64/digilent/adept/libdpcomm.so.2
#9  0x00007fffefd498dc in ?? () from /usr/lib64/digilent/adept/libdpcomm.so.2
#10 0x00007ffff395a6ba in start_thread (arg=0x7fffc4907700) at pthread_create.c:333
#11 0x00007ffff48b941d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Running strace this line appears 3 times:

open("/dev/bus/usb/002/004", O_RDWR)    = -1 EACCES (Permission denied)

At a glance this appears to be a permission issue for accessing the USB port/driver for this device; is there a recommended adjustment or fix for this at this time?

Link to comment
Share on other sites

5 answers to this question

Recommended Posts

Thanks @JColvin,

I should add that the "/etc/udev/rules.d/52-digilent-usb.rules" file looks correct in that it should make the port available to all users. The permissions on the corresponding file are however not configured as expected.

crw-rw-r-- 1 root root 189, 131  4月 11 11:57 /dev/bus/usb/002/004

If I force a change in the permissions from the shell I can launch as a standard user, which may point to a more general system issue though it is very specific to this device for some reason.

 

Link to comment
Share on other sites

Thanks for checking,

I have 2 other FTDI USB interfaces / devices running here so I may try a check at a later date without those attached in order to ascertain whether or not there is some sort of interplay: unlikely but worth a shot.  Since the system should assign the permissions when the device is attached I don't believe that there is anything particularly non-standard in my installation but I'll have a closer look (if time allows) post a result here for other.

Link to comment
Share on other sites

Archived

This topic is now archived and is closed to further replies.

×
×
  • Create New...