[digikam] [Bug 422502] New: Core dumped (Assert failed QList index out of range)

https://bugs.kde.org/show_bug.cgi?id=422502 Bug ID: 422502 Summary: Core dumped (Assert failed QList index out of range) Product: digikam Version: 6.4.0 Platform: Archlinux Packages OS: Linux Status: REPORTED

[digikam] [Bug 422502] Core dumped (Assert failed QList index out of range)

https://bugs.kde.org/show_bug.cgi?id=422502 --- Comment #3 from yaogen --- Reported this last night and it's solved when I wake up. Incredible :-) Would you still need the GDB backtrace or you feel that your fix "was it" ? Thanks -- You are receiving this mail because: You a

[digikam] [Bug 422502] Core dumped (Assert failed QList index out of range)

https://bugs.kde.org/show_bug.cgi?id=422502 --- Comment #5 from yaogen --- After doing 1,2,3 above for a while I got the following out of gdb [Thread 0x7fff2c915700 (LWP 1266290) exited] --Type for more, q to quit, c to continue without paging-- [Switching to Thread 0x7fffd5a88700 (LWP 846207

[digikam] [Bug 422502] Core dumped (Assert failed QList index out of range)

https://bugs.kde.org/show_bug.cgi?id=422502 --- Comment #7 from yaogen --- Indeed, those are Exiv2 thrown stuff. I only caught those by following the instructions to use 'catch throw'. But after removing that breakpoint and letting the Assertion hit, I got the following: ASSERT failur

[digikam] [Bug 422502] Core dumped (Assert failed QList index out of range)

https://bugs.kde.org/show_bug.cgi?id=422502 --- Comment #8 from yaogen --- Got another crash, slightly different output (and no ASSERT string) Maybe related, maybe not. *shrug* Thread 1 "digikam" received signal SIGABRT, Aborted. 0x74cff355 in raise () from /usr/lib/libc.so.