[Digikam-devel] [Bug 290961] digiKam crashes after closing the configure dialog

Ananta Palani anantapalani at gmail.com
Sun Jan 8 16:50:58 GMT 2012


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





--- Comment #5 from Ananta Palani <anantapalani gmail com>  2012-01-08 16:50:57 ---
(In reply to comment #4)
> I used the official Windows installer from sourceforge
> (digiKam-installer-2.5.0-win32.exe). It don't contents gdb, but i downloaded it
> separately.

It does have it, but no matter. The one you downloaded should be fine.

> The line "set disable-address-randomization off" will cause the error "No
> symbol table is loaded.  Use the "file" command.". Is this a problem?

No, it isn't a problem. The command just tells gdb to allow address
randomization so that if the crash occurs because of a race condition when not
debugging then it is more likely to crash while debugging (sometimes a crash
will not occur while debugging because gdb will turn off address randomization
so behavior will be different).

> When digiKam freezes, i have to kill it using the Windows Task-Manager. Before
> it was not possible to type something into the gdb console. Then the command
> "bt" says "No stack.".

How long do you wait before you kill it? If digiKam actually crashed gdb would
inform you and then you can type 'bt'. If you can't type 'bt' then it hasn't
crashed yet and digiKam is simply waiting for something to happen, but it
hasn't crashed. If you kill it in the task manager, there is no stack because
the program is gone! You must wait until gdb informs you that there was a crash
(gdb will give a message like "Program received signal SIGSEGV, Segmentation
fault" or similar) and then you can type 'bt'. This could take quite a few
minutes.

Also, during all of this does your hard drive have high disk-activity? Does it
say "Scanning collection0%" at the bottom-left of digiKam's main window?

-- 
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