Re: gnokii 0.6.29 and 0.6.32 master segfaults

[Charles]

On 25/04/12 20:10, Daniele Forsi wrote:
> change the library search path at runtime to look first in the
> directory containing the new libusb-0.1.so.4 or what gnokii searches
> (use ldd gnokii to see needed libraries)
> 
> looking at your output it could be something like:
> LD_LIBRARY_PATH=/tmp/package-libusb/usr/lib64/ gnokii --identify

address@hidden:~$ ldd /usr/bin/gnokii
        linux-vdso.so.1 =>  (0x00007fff990c6000)
        libgnokii.so.7 => /usr/lib64/libgnokii.so.7 (0x00007f02a4274000)
        libXpm.so.4 => /usr/lib64/libXpm.so.4 (0x00007f02a4063000)
        libX11.so.6 => /usr/lib64/libX11.so.6 (0x00007f02a3d22000)
        libxcb.so.1 => /usr/lib64/libxcb.so.1 (0x00007f02a3b06000)
        libXau.so.6 => /usr/lib64/libXau.so.6 (0x00007f02a3903000)
        libXdmcp.so.6 => /usr/lib64/libXdmcp.so.6 (0x00007f02a36fd000)
        libdl.so.2 => /lib64/libdl.so.2 (0x00007f02a34de000)
        libbluetooth.so.3 => /usr/lib64/libbluetooth.so.3 (0x00007f02a32c3000)
        libusb-0.1.so.4 => /usr/lib64/libusb-0.1.so.4 (0x00007f02a30bd000)
        libusb-1.0.so.0 => /usr/lib64/libusb-1.0.so.0 (0x00007f02a2eb0000)
        libical.so.0 => /usr/lib64/libical.so.0 (0x00007f02a2c53000)
        libpthread.so.0 => /lib64/libpthread.so.0 (0x00007f02a2a34000)
        libglib-2.0.so.0 => /usr/lib64/libglib-2.0.so.0 (0x00007f02a271d000)
        librt.so.1 => /lib64/librt.so.1 (0x00007f02a2514000)
        libreadline.so.5 => /usr/lib64/libreadline.so.5 (0x00007f02a22d5000)
        libncurses.so.5 => /usr/lib64/libncurses.so.5 (0x00007f02a2084000)
        libc.so.6 => /lib64/libc.so.6 (0x00007f02a1cde000)
        /lib64/ld-linux-x86-64.so.2 (0x00007f02a451b000)

Running ...
LD_LIBRARY_PATH=/tmp/libusb-1.0.8/libusb gnokii --identify
... did not produce the expected debug prints.

So I built packages of gnokii with debug prints and usblib with debug
prints and installed both of them and tested again, setting LIBUSB_DEBUG:

address@hidden:~$ export LIBUSB_DEBUG=3
address@hidden:~$ gnokii --identify
GNOKII Version 0.6.32git
LOG: debug mask is 0x1
Config read from file /home/c/.config/gnokii/config.
Lockfile /var/lock/LCK..1 is stale. Overriding it...
phone instance config:
model = series40
port = 1
connection = dku2libusb
initlength = default
serial_baudrate = 19200
serial_write_usleep = -1
handshake = software
require_dcd = 0
smsc_timeout = 10
rfcomm_channel = 0
sm_retry = 0
Connecting
overrun: 1010 0
device: opening device USB
Ignoring extra header, type 171, length 5
Found FBUS interface
libusb:error [op_open] libusb couldn't open USB device
/dev/bus/usb/003/003: Permission denied.
libusb requires write access to USB device nodes.

Before get_iface_string calls   \
devinstance: 0x7fd55b3fe518      } From gnokii
current: 0x65e5e0               /
usb_get_string_simple: running  \
dev: (nil), desc_index: 1       /  From compat lib
Segmentation fault

address@hidden:~$ ls -l /dev/bus/usb/003/003
crw-rw-r-- 1 root root 189, 258 Apr 26 13:59 /dev/bus/usb/003/003

How should I go from here?

Investigate the /dev file's permissions?

In gnokii's usbfbus_find_interfaces, should I print usb_handle?  If so
what is its type, what does usb_open return (and incidentally, how can I
find the header file that declares it?)?

In gnokii's get_iface_string, should I print all the values which are
passed to usb_get_string_simple?  And if so what are their types?

In libusb's libusb_get_string_descriptor_ascii, should I add debug
prints to  identify where it segfaults, starting before the first use of
dev in the call to libusb_get_string_descriptor?