Project

General

Profile

Bug #9216

dt crash on Mac

Added by Anonymous about 7 years ago.

Status:
Closed: invalid
Priority:
Low
Assignee:
-
Category:
-
Target version:
-
Start date:
01/29/2013
Due date:
% Done:

0%

Estimated time:
Affected Version:
1.1.2
System:
Mac OS X
bitness:
64-bit
hardware architecture:
amd64/x86

Description

Crash after selecting Quit from the Apple menu. Crash report included.
Pls. advise if you prefer Mac reports or Terminal.

History

#1 Updated by James C. McPherson about 7 years ago

Please provide plain text attachments, or paste stack traces directly into the bug text pane.

========
Process: darktable-bin [1504]
Path: /Applications/darktable.app/Contents/MacOS/darktable-bin
Identifier: org.darktable
Version: 1.1.2 (1.1.2.0)
Code Type: X86-64 (Native)
Parent Process: launchd [114]

Date/Time: 2013-01-28 21:33:56.042 -0500
OS Version: Mac OS X 10.6.8 (10K549)
Report Version: 6

Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0x0000000104df6520
Crashed Thread: 0 Dispatch queue: com.apple.main-thread

Thread 0 Crashed: Dispatch queue: com.apple.main-thread
0 ??? 0x0000000104df6520 0 + 4376716576

Thread 1: org.libusb.device-detach
0 libSystem.B.dylib 0x00007fff822e3d7a mach_msg_trap + 10
1 libSystem.B.dylib 0x00007fff822e43ed mach_msg + 59
2 com.apple.CoreFoundation 0x00007fff85fa1902 __CFRunLoopRun + 1698
3 com.apple.CoreFoundation 0x00007fff85fa0d8f CFRunLoopRunSpecific + 575
4 com.apple.CoreFoundation 0x00007fff85fa0b16 CFRunLoopRun + 70
5 libusb-1.0.0.dylib 0x0000000100cb5f81 event_thread_main + 577
6 libSystem.B.dylib 0x00007fff8231cfd6 _pthread_start + 331
7 libSystem.B.dylib 0x00007fff8231ce89 thread_start + 13

Thread 2: Dispatch queue: com.apple.libdispatch-manager
0 libSystem.B.dylib 0x00007fff822fcc0a kevent + 10
1 libSystem.B.dylib 0x00007fff822feadd _dispatch_mgr_invoke + 154
2 libSystem.B.dylib 0x00007fff822fe7b4 _dispatch_queue_invoke + 185
3 libSystem.B.dylib 0x00007fff822fe2de _dispatch_worker_thread2 + 252
4 libSystem.B.dylib 0x00007fff822fdc08 _pthread_wqthread + 353
5 libSystem.B.dylib 0x00007fff822fdaa5 start_wqthread + 13

Thread 3:
0 libSystem.B.dylib 0x00007fff822fda2a __workq_kernreturn + 10
1 libSystem.B.dylib 0x00007fff822fde3c _pthread_wqthread + 917
2 libSystem.B.dylib 0x00007fff822fdaa5 start_wqthread + 13

Thread 4:
0 libSystem.B.dylib 0x00007fff8231ea6a __semwait_signal + 10
1 libSystem.B.dylib 0x00007fff82322881 _pthread_cond_wait + 1286
2 libgdk-quartz-2.0.0.dylib 0x00000001004633c1 select_thread_func + 257
3 libSystem.B.dylib 0x00007fff8231cfd6 _pthread_start + 331
4 libSystem.B.dylib 0x00007fff8231ce89 thread_start + 13

Thread 5:
0 libSystem.B.dylib 0x00007fff822fda2a __workq_kernreturn + 10
1 libSystem.B.dylib 0x00007fff822fde3c _pthread_wqthread + 917
2 libSystem.B.dylib 0x00007fff822fdaa5 start_wqthread + 13

Thread 0 crashed with X86 Thread State (64-bit):
rax: 0x0000000104df6520 rbx: 0x0000000000000001 rcx: 0x000000014eeb00a0 rdx: 0x000000000000053d
rdi: 0x0000000141060120 rsi: 0x0000000000000683 rbp: 0x0000000141060000 rsp: 0x00007fff5fbfc008
r8: 0x00000001003a77e8 r9: 0x0000000000000004 r10: 0x0000000000000001 r11: 0x0000000000000010
r12: 0x0000000000000683 r13: 0x000000000000053d r14: 0x00007fff5fbfc198 r15: 0x00000001000af0e0
rip: 0x0000000104df6520 rfl: 0x0000000000010202 cr2: 0x0000000104df6520

[snipping the list of libraries loaded] ========

Thread 0 is the one which encountered the segv. Looking at the info above

0 ??? 0x0000000104df6520 0 + 4376716576

The offset (+ 4376716576) is 0x104df6520 which, you'll note, is reported
as the contents of %rax, %rip and %cr2. This is a little unusual - %cr2
is (iirc) most often used to report the results of test opcodes.

Something has smashed the stack on this installation. If only there was
something akin to Solaris' libumem which Mac OSX 10.6.8 could make use of
to help figure this out.

#2 Updated by Simon Spannagel about 7 years ago

  • System set to Mac OS X

#3 Updated by James C. McPherson about 7 years ago

  • Status changed from New to Closed: invalid

Since the submitter has uninstalled darktable and removed their redmine account, closing this as 'invalid'

Also available in: Atom PDF

Go to top