Bug 309769 - Crash on startup: 'Program received signal SIGILL, Illegal instruction.' (libopencv_nonfree)
Summary: Crash on startup: 'Program received signal SIGILL, Illegal instruction.' (lib...
Status: RESOLVED FIXED
Alias: None
Product: digikam
Classification: Applications
Component: Faces-Engine (show other bugs)
Version: 2.9.0
Platform: Exherbo Linux
: NOR major
Target Milestone: ---
Assignee: Digikam Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-11-08 20:33 UTC by Markus Schmits
Modified: 2019-12-23 06:05 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In: 7.0.0


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Markus Schmits 2012-11-08 20:33:44 UTC
Application terminates before main window is shown with 'Program received signal SIGILL, Illegal instruction.' See backtrace attached for more information.

Reproducible: Always

Steps to Reproduce:
1. Compile from source with no errors coming up.
2. Start application.
3.
Actual Results:  
GNU gdb (GDB) 7.5
Copyright (C) 2012 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "i686-pc-linux-gnu".
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>...
Reading symbols from /usr/bin/digikam...Reading symbols from /usr/lib/debug/usr/bin/digikam.debug...(no debugging symbols found)...done.
(no debugging symbols found)...done.
(gdb) run
Starting program: /usr/bin/digikam 
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/libthread_db.so.1".
Traceback (most recent call last):
  File "/usr/share/gdb/auto-load/usr/lib/libgobject-2.0.so.0.3200.4-gdb.py", line 9, in <module>
    from gobject import register
  File "/usr/share/glib-2.0/gdb/gobject.py", line 3, in <module>
    import gdb.backtrace
ImportError: No module named backtrace

Program received signal SIGILL, Illegal instruction.
0xb1f0393f in cv::SIFT::SIFT(int, int, double, double, double) () from /usr/lib/libopencv_nonfree.so.2.4
(gdb) bt
#0  0xb1f0393f in cv::SIFT::SIFT(int, int, double, double, double) () from /usr/lib/libopencv_nonfree.so.2.4
#1  0xb1f02480 in cv::createSIFT() () from /usr/lib/libopencv_nonfree.so.2.4
#2  0xb1f02795 in cv::initModule_nonfree() () from /usr/lib/libopencv_nonfree.so.2.4
#3  0xb1e2a50f in _GLOBAL__sub_I_matchers.cpp () from /usr/lib/libopencv_stitching.so.2.4
#4  0xb7fed963 in call_init () from /lib/ld-linux.so.2
#5  0xb7fedaa4 in _dl_init_internal () from /lib/ld-linux.so.2
#6  0xb7fe01ef in _dl_start_user () from /lib/ld-linux.so.2



Compiled packages:
opencv-2.4.2
digikam-2.9.0
Comment 1 caulier.gilles 2012-11-08 20:48:53 UTC
It crash in OpenCV library, not digiKam. Check your system...

Gilles Caulier
Comment 2 Markus Schmits 2012-11-08 21:26:09 UTC
(In reply to comment #1)
> It crash in OpenCV library, not digiKam. Check your system...
> 
> Gilles Caulier

Sorry bothering you then. But this lib is required by digikam, so a compile without it would fail? I recheck using an older version of opencv then, as I did not having problems in the past with digikam.
Thanks.

Markus Schmits
Comment 3 caulier.gilles 2019-12-23 06:05:10 UTC
Problem is fixed with new 7.0.0-beta1 through this long story from this bug

https://bugs.kde.org/show_bug.cgi?id=399923

You can test digiKam 7.0.0-beta1 with bundle available here:

https://download.kde.org/unstable/digikam/

Don't hesitate to give us a fresh feedback about his entry.

Thanks in advance

Gilles Caulier