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

--- Comment #49 from Joseph Reagle <joseph.2...@reagle.org> ---
Crash report still present in 6.3.0

Process:               digikam [29398]
Path:                  /opt/digikam/*/digikam.app/Contents/MacOS/digikam
Identifier:            digikam
Version:               6.3.0 (6.3.0-git)
Code Type:             X86-64 (Native)
Parent Process:        ??? [1]
Responsible:           digikam [29398]
User ID:               502

Date/Time:             2019-08-05 08:19:17.875 -0400
OS Version:            Mac OS X 10.14.6 (18G84)
Report Version:        12
Bridge OS Version:     3.6 (16P6568)
Anonymous UUID:        A3B78802-9A75-4BA9-6ADB-E84F5DFAEEF3


Time Awake Since Boot: 1000000 seconds

System Integrity Protection: enabled

Crashed Thread:        0  Dispatch queue: com.apple.main-thread

Exception Type:        EXC_BAD_ACCESS (SIGSEGV)
Exception Codes:       KERN_PROTECTION_FAILURE at 0x00007ffeea24a330
Exception Note:        EXC_CORPSE_NOTIFY

Termination Signal:    Segmentation fault: 11
Termination Reason:    Namespace SIGNAL, Code 0xb
Terminating Process:   exc handler [29398]

VM Regions Near 0x7ffeea24a330:
    STACK GUARD            00007ffee624b000-00007ffee9a4b000 [ 56.0M] ---/rwx
SM=NUL  stack guard for thread 0
--> Stack                  00007ffee9a4b000-00007ffeea24b000 [ 8192K] rw-/rwx
SM=SHM  thread 0
    Submap                 00007fff00000000-00007fff80000000 [  2.0G] r--/rwx
SM=SHM  machine-wide VM submap

Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0   ???                                 0x00007ffeea24a330 0 + 140732826690352
...

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to