| Summary: | Digikam won't start: *** Error in `digikam': realloc(): invalid pointer: 0x0000000000c14260 *** | ||
|---|---|---|---|
| Product: | [Applications] digikam | Reporter: | John O'Shaughnessy <johnoshaugh> |
| Component: | Portability-Runtime | Assignee: | Digikam Developers <digikam-bugs-null> |
| Status: | RESOLVED FIXED | ||
| Severity: | crash | CC: | caulier.gilles |
| Priority: | NOR | ||
| Version: | 4.6.0 | ||
| Target Milestone: | --- | ||
| Platform: | openSUSE | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | 4.8.0 | |
| Sentry Crash Report: | |||
|
Description
John O'Shaughnessy
2015-01-19 03:11:43 UTC
Install debug packages and run digiKam into GDB to get a suitable backtrace, as explained here : https://www.digikam.org/contrib Gilles Caulier running gdb digikam ...... run just reproduced exactly what I've already sent you before, spread over the details and information boxes.... the problem is its way too many lines to include in the comments, so how to send you? plus you have this already... (gdb) catch throw Catchpoint 1 (throw) (gdb) run Starting program: /usr/bin/digikam warning: the debug information found in "/usr/lib/debug//usr/lib64/libdigikamcore.so.4.6.0.debug" does not match "/usr/lib64/libdigikamcore.so.4.6.0" (CRC mismatch). warning: the debug information found in "/usr/lib/debug/usr/lib64/libdigikamcore.so.4.6.0.debug" does not match "/usr/lib64/libdigikamcore.so.4.6.0" (CRC mismatch). [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib64/libthread_db.so.1". *** Error in `/usr/bin/digikam': realloc(): invalid pointer: 0x0000000000c14260 *** ======= Backtrace: ========= /lib64/libc.so.6(+0x7283f)[0x7ffff09b583f] /lib64/libc.so.6(+0x77c1e)[0x7ffff09bac1e] /lib64/libc.so.6(realloc+0x26a)[0x7ffff09bedfa] /usr/lib64/libQt5Core.so.5(_ZN9QListData7reallocEi+0x1e)[0x7fffdfe0e90e] /usr/lib64/libQt5Core.so.5(_ZN9QListData6appendEi+0x6a)[0x7fffdfe0e9ca] /usr/lib64/libQt5Core.so.5(+0x1d6f5c)[0x7fffdfed6f5c] /usr/lib64/libQt5Core.so.5(_Z21qRegisterResourceDataiPKhS0_S0_+0x2b9)[0x7fffdfed3409] /usr/lib64/libQt5Core.so.5(+0x807e3)[0x7fffdfd807e3] /lib64/ld-linux-x86-64.so.2(+0xeaaa)[0x7ffff7deaaaa] /lib64/ld-linux-x86-64.so.2(+0xeb93)[0x7ffff7deab93] /lib64/ld-linux-x86-64.so.2(+0x11ba)[0x7ffff7ddd1ba] ======= Memory map: ======== 00400000-00a0a000 r-xp 00000000 08:07 2373690 /usr/bin/digikam 00c09000-00c0a000 r--p 00609000 08:07 2373690 /usr/bin/digikam 00c0a000-00c15000 rw-p 0060a000 08:07 2373690 /usr/bin/digikam ********........for thousands of lines until.......******************* ffff7ffd000-7ffff7ffe000 rw-p 00021000 08:07 525248 /lib64/ld-2.20.so 7ffff7ffe000-7ffff7fff000 rw-p 00000000 00:00 0 7ffffffde000-7ffffffff000 rw-p 00000000 00:00 0 [stack] ffffffffff600000-ffffffffff601000 r-xp 00000000 00:00 0 [vsyscall] Program received signal SIGABRT, Aborted. 0x00007ffff09780f7 in raise () from /lib64/libc.so.6 (gdb) ^CQuit (gdb) bt produces: (gdb) bt #0 0x00007ffff09780f7 in raise () at /lib64/libc.so.6 #1 0x00007ffff09794ca in abort () at /lib64/libc.so.6 #2 0x00007ffff09b5844 in () at /lib64/libc.so.6 #3 0x00007ffff09bac1e in malloc_printerr () at /lib64/libc.so.6 #4 0x00007ffff09bedfa in realloc () at /lib64/libc.so.6 #5 0x00007fffdfe0e90e in QListData::realloc(int) () at /usr/lib64/libQt5Core.so.5 #6 0x00007fffdfe0e9ca in QListData::append(int) () at /usr/lib64/libQt5Core.so.5 #7 0x00007fffdfed6f5c in () at /usr/lib64/libQt5Core.so.5 #8 0x00007fffdfed3409 in qRegisterResourceData(int, unsigned char const*, unsigned char const*, unsigned char const*) () at /usr/lib64/libQt5Core.so.5 #9 0x00007fffdfd807e3 in () at /usr/lib64/libQt5Core.so.5 #10 0x00007ffff7deaaaa in call_init.part () at /lib64/ld-linux-x86-64.so.2 #11 0x00007ffff7deab93 in _dl_init_internal () at /lib64/ld-linux-x86-64.so.2 #12 0x00007ffff7ddd1ba in _dl_start_user () at /lib64/ld-linux-x86-64.so.2 #13 0x0000000000000001 in () #14 0x00007fffffffe437 in () #15 0x0000000000000000 in () (gdb) OK, it seems like no more responses here. However, update: Digikam has been updated a couple of times since and is now working from today. I've know idea what could have caused this.... so I don't know how the issue has been resolved. Nothing in my desktop configuration has changed. Sound like binary compatibility issues with your distro packages. It's an usual case... Gilles Caulier (In reply to Gilles Caulier from comment #4) > Sound like binary compatibility issues with your distro packages. It's an > usual case... > > Gilles Caulier I see, Gilles. What could I do to prevent something like this from happening again? Good question... Nothing from user point. digiKAm and all shared lib managed by digiKAm must be recompiled in case of a dependency is updated by packagers. It's a packaging problem in fact. Me, i recompile digiKam myself. So if i update my system, recompiling whole program prevent this kind of dysfunction. I'm developer also, so this workflow is not acceptable by end users. Gilles Caulier Right, thanks for your honesty Gilles.. that's the one thing I appreciate about open source. It might not be acceptable, but at least youre not pulling the wool over my eyes and telling me only how I'd like to hear it. I use Digikam instead of Adobe Bridge and the few inconveniences are worth it to me. |