[Digikam-devel] [Bug 274713] Digikam crashed unexpectedly

Marcel Wiesweg marcel.wiesweg at gmx.de
Sat Jun 11 16:19:02 CEST 2011


Marcel Wiesweg <marcel.wiesweg at gmx.de> changed:

           What    |Removed                     |Added
             Status|UNCONFIRMED                 |RESOLVED
         Resolution|                            |UPSTREAM

--- Comment #3 from Marcel Wiesweg <marcel wiesweg gmx de>  2011-06-11 16:18:59 ---
There is not much difference between calling abort() or doing ((int*)0)++. If
libavahi chooses to call abort in the digikam process, it will tear down the
process immediately. And it seems quite consistent that a software dealing with
network awareness will show activity after and change in network state.

So this is an upstream bug in libavahi unless
- a backtrace, possibly produced from running under gdb instead of core dump
analysis after the crash, suddenly shows the crash occured in digikam code, or
- the crash can be reproduced (suspend + resume) with varying backtraces, and
- valgrind shows invalid memory operations by digikam causing memory corruption
(probably coninciding with the previous point)

At the moment, there is nothing in digikam listening to network state change,
so I doubt the hypothesis.

Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

More information about the Digikam-devel mailing list