[LINUX/OpenSUSE 13.2] - Crash on CDeckLinkNotification

Ask software engineering and SDK questions for developers working on Mac OS X, Windows or Linux.
  • Author
  • Message
Offline

Sylvain Fabre

  • Posts: 3
  • Joined: Wed Dec 02, 2015 2:19 pm

[LINUX/OpenSUSE 13.2] - Crash on CDeckLinkNotification

PostWed Dec 02, 2015 2:29 pm

Hi all,

We are testing a Deckling Duo in a Core-i7 PC, OpenSUSE 13.2, DesktopVideo 10.5.2 64 bits, we have a seg fault when using the samples. The crash occurs always at the same call : CDeckLinkNotification::run()

For example :
Code: Select all
gdb ./DeviceList
....
=============== DeckLink SDI ===============

Attribute list:
 Serial port present ?                    No
 Device Persistent ID:                    Not Supported on this device
 Device Topological ID:                   2e0400
 Number of sub-devices:                   2
 Sub-device index:                        0
 Number of audio channels:                8
 Input mode detection supported ?         Yes
 Full duplex operation supported ?        No
 Internal keying supported ?              Yes
 External keying supported ?              No
 HD-mode keying supported ?               No

[New Thread 0x7ffff55ec700 (LWP 8716)]
Supported video output display modes and pixel formats:
 NTSC                    720 x 486         29.97 FPS     8-bit YUV      10-bit YUV      ------          ------          ------          ------          ------          ------          ------

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7ffff5ded700 (LWP 8715)]
0x00007ffff7bd01b8 in __lll_unlock_elision () from /lib64/libpthread.so.0
Missing separate debuginfos, use: zypper install desktopvideo-debuginfo-10.5.2-a5.x86_64
(gdb) bt
#0  0x00007ffff7bd01b8 in __lll_unlock_elision () from /lib64/libpthread.so.0
#1  0x00007ffff686d189 in CDeckLinkNotification::run() () from /usr/lib64/libDeckLinkAPI.so
#2  0x00007ffff686d239 in ?? () from /usr/lib64/libDeckLinkAPI.so
#3  0x00007ffff7bc70a4 in start_thread () from /lib64/libpthread.so.0
#4  0x00007ffff6ed908d in clone () from /lib64/libc.so.6


It seems to be related to the Duo board, as the same drivers in another computer with a Decklink Monitor board are working properly.

Any fix or hint ?

Thanks,
Sylvain FABRE

Return to Software Developers

Who is online

Users browsing this forum: No registered users and 15 guests