segmentation fault ./digikam

Gilles Caulier caulier.gilles at gmail.com
Fri Jul 14 15:47:47 BST 2023


Le ven. 14 juil. 2023 à 14:41, Benoit <benoitlst at ouvaton.org> a écrit :

>
>
> Thread 1 "digikam" received signal SIGSEGV, Segmentation fault.
> 0x00007ffff510c848 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5
>
> I'm on debian stable and it's installed in this version : 5.15.8
>
> Cf.
> https://packages.debian.org/bookworm/libqt5core5a
>
>
>
>
>
> --
> (gdb) run
> The program being debugged has been started already.
> Start it from the beginning? (y or n) y
> Starting program: /div/digikam/digikam-build14-07-2023/bin/digikam
> [Thread debugging using libthread_db enabled]
> Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
> [New Thread 0x7fffdc1af6c0 (LWP 56034)]
> [New Thread 0x7fffdb9ae6c0 (LWP 56035)]
> [New Thread 0x7fffd31ad6c0 (LWP 56036)]
> [New Thread 0x7fffc29ac6c0 (LWP 56037)]
> [New Thread 0x7fffba1ab6c0 (LWP 56038)]
> [New Thread 0x7fffb99aa6c0 (LWP 56039)]
> [New Thread 0x7fffa91a96c0 (LWP 56040)]
> [New Thread 0x7fff9fdff6c0 (LWP 56041)]
> [New Thread 0x7fff9d1ff6c0 (LWP 56042)]
> [New Thread 0x7fff9c9fe6c0 (LWP 56043)]
> [New Thread 0x7fff8f5ff6c0 (LWP 56044)]
> [New Thread 0x7fff8edfe6c0 (LWP 56045)]
> [New Thread 0x7fff8e1fd6c0 (LWP 56046)]
> [New Thread 0x7fff8d7fc6c0 (LWP 56047)]
> [New Thread 0x7fff8cffb6c0 (LWP 56048)]
> [New Thread 0x7fff6ffff6c0 (LWP 56049)]
> [New Thread 0x7fff6f7fe6c0 (LWP 56050)]
> [Thread 0x7fff6f7fe6c0 (LWP 56050) exited]
> [New Thread 0x7fff6f7fe6c0 (LWP 56051)]
> [New Thread 0x7fff6effd6c0 (LWP 56052)]
> [Thread 0x7fffb99aa6c0 (LWP 56039) exited]
> [Thread 0x7fffa91a96c0 (LWP 56040) exited]
> [Thread 0x7fffba1ab6c0 (LWP 56038) exited]
> [Thread 0x7fffc29ac6c0 (LWP 56037) exited]
> [Thread 0x7fffd31ad6c0 (LWP 56036) exited]
> [Thread 0x7fffdb9ae6c0 (LWP 56035) exited]
> [Thread 0x7fffdc1af6c0 (LWP 56034) exited]
> [Detaching after fork from child process 56053]
>
> Thread 1 "digikam" received signal SIGSEGV, Segmentation fault.
> 0x00007ffff510c848 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5
>
>
> (gdb) list
> 1       in ../sysdeps/x86_64/crtn.S
>
>
> --
>
> --
>
>
>
> Le vendredi 14 juillet 2023 à 13:57 +0200, Gilles Caulier a écrit :
> >
> >
> > Le ven. 14 juil. 2023 à 10:49, Benoit <benoitlst at ouvaton.org> a écrit :
> > > Hello,
> > >
> > > I built digiKam 8.1.0 and I have a segmentation fault
> > >
> > > The compiler options I used :
> > >
> > > export VERBOSE=1
> > > export QTDIR=/usr/lib/qt5
> > > export PATH=$QTDIR/bin:$PATH
> > > cmake -DCMAKE_INSTALL_PREFIX=/div/local/bin/digikam -
> > > DCMAKE_BUILD_TYPE=release
> > > -DENABLE_MEDIAPLAYER="OFF" ../digikam-src
> > >
> > > make
> > >
> > > The compilation succeeded,
> > > it happens after the configuration wizard
> > >
> > > thanks
> > >
> > > --
> > > Benoit
> > >
> > >
> > > What’s the GDB backtrack of the crash ?
> > >
> >
> >
> > Gilles Caulier
> >
> > --
> > Send with Gmail Mobile
>
> There is nothing to see from digiKam code. Sound like a binary
compatibility issue with qt libraries. Try to clean up all compilation and
try again from scratch--
Send with Gmail Mobile
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/digikam-users/attachments/20230714/0ad54606/attachment.htm>


More information about the Digikam-users mailing list