[Digikam-devel] [Bug 303992] Digikam is closing after opening any file dialog

[Rafael]

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

--- Comment #10 from Rafael <rmrcbm at gmail.com> ---
Thank you Andrew. This is the result after I did what you told me.

ModLoad: 00000000`013e0000 00000000`0183b000   digikam.exe
ModLoad: 00000000`775a0000 00000000`77749000   ntdll.dll
ModLoad: 00000000`77780000 00000000`77900000   ntdll32.dll
ModLoad: 00000000`74e00000 00000000`74e3f000   C:\Windows\SYSTEM32\wow64.dll
ModLoad: 00000000`74da0000 00000000`74dfc000
C:\Windows\SYSTEM32\wow64win.dll
ModLoad: 00000000`74d90000 00000000`74d98000
C:\Windows\SYSTEM32\wow64cpu.dll
(188c.1f9c): Break instruction exception - code 80000003 (first chance)
ntdll!LdrpDoDebuggerBreak+0x30:
00000000`7764cb60 cc              int     3

I don't know what's the problem neither.

2012/8/2 Andrew Goodbody <ajg02 at elfringham.co.uk>

> https://bugs.kde.org/show_bug.cgi?id=303992
>
> Andrew Goodbody <ajg02 at elfringham.co.uk> changed:
>
>            What    |Removed                     |Added
>
> ----------------------------------------------------------------------------
>                  CC|                            |ajg02 at elfringham.co.uk
>
> --- Comment #9 from Andrew Goodbody <ajg02 at elfringham.co.uk> ---
> The issue with ntdll.dll is that WinDbg cannot find the symbols for
> printing in
> the backtrace. You can configure WinDbg to automatically download any
> Windows
> symbols it needs. See the article at this link
>
> http://features.techworld.com/operating-systems/3275067/solving-windows-7-crashes-with-debugging-tools/?pn=2
> This does not explain why the code is ending up at the breakpoint though.
>
> --
> You are receiving this mail because:
> You are on the CC list for the bug.
> You reported the bug.
>

-- 
You are receiving this mail because:
You are the assignee for the bug.