[digikam] [Bug 365684] Crash when deleting a tag from the list of tags

[via KDE Bugzilla]

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

--- Comment #12 from caulier.gil...@gmail.com ---
Which OSX version do you use ?

Give me more information about your collection. Where are stored your images ?
Which kind of images do you use ? JPEG, RAW, TIFF ?

Gilles Caulier

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

[digikam] [Bug 365684] Crash when deleting a tag from the list of tags

[via KDE Bugzilla]

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

--- Comment #11 from caulier.gil...@gmail.com ---
Which OSX version do you use ?

Give me more information about your collection. Where are stored your images ?
Which kind of images do you use ? JPEG, RAW, TIFF ?

Gilles Caulier

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

[digikam] [Bug 365684] Crash when deleting a tag from the list of tags

[via KDE Bugzilla]

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

--- Comment #10 from caulier.gil...@gmail.com ---
yes digiKam bundle must have debug symbols.

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

[digikam] [Bug 365684] Crash when deleting a tag from the list of tags

[Olli Lupton via KDE Bugzilla]

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

--- Comment #9 from Olli Lupton  ---
I tried catching the crash with Xcode, but there is very little information
there.
Are the precompiled bundles on http://download.kde.org/stable/digikam/ supposed
to have debug symbols?  Xcode just shows the instructions, which are rather
unhelpful.

QtCore`QSortFilterProxyModel::parent:
0x10da90ff0 <+0>:   pushq  %rbp
0x10da90ff1 <+1>:   movq   %rsp, %rbp
0x10da90ff4 <+4>:   pushq  %rbx
0x10da90ff5 <+5>:   subq   $0x38, %rsp
0x10da90ff9 <+9>:   movq   %rdi, %rbx
0x10da90ffc <+12>:  movq   (%rdx), %rax
0x10da90fff <+15>:  testl  %eax, %eax
0x10da91001 <+17>:  js 0x10da91019   ; <+41>
0x10da91003 <+19>:  shrq   $0x20, %rax
0x10da91007 <+23>:  testl  %eax, %eax
0x10da91009 <+25>:  js 0x10da91019   ; <+41>
0x10da9100b <+27>:  movq   0x8(%rsi), %rax
0x10da9100f <+31>:  movq   0x10(%rdx), %rcx
0x10da91013 <+35>:  cmpq   0x8(%rax), %rcx
0x10da91017 <+39>:  je 0x10da9103a   ; <+74>
0x10da91019 <+41>:  movq   $-0x1, (%rbx)
0x10da91020 <+48>:  movq   $0x0, 0x10(%rbx)
0x10da91028 <+56>:  movq   $0x0, 0x8(%rbx)
0x10da91030 <+64>:  movq   %rbx, %rax
0x10da91033 <+67>:  addq   $0x38, %rsp
0x10da91037 <+71>:  popq   %rbx
0x10da91038 <+72>:  popq   %rbp
0x10da91039 <+73>:  retq   
0x10da9103a <+74>:  movq   0x8(%rdx), %rax
0x10da9103e <+78>:  movq   0x28(%rax), %rax
->  0x10da91042 <+82>:  movq   0x20(%rax), %rcx
0x10da91046 <+86>:  movq   %rcx, -0x10(%rbp)
0x10da9104a <+90>:  movq   0x10(%rax), %rcx
0x10da9104e <+94>:  movq   0x18(%rax), %rax
0x10da91052 <+98>:  movq   %rax, -0x18(%rbp)
0x10da91056 <+102>: movq   %rcx, -0x20(%rbp)
0x10da9105a <+106>: movq   (%rsi), %rax
0x10da9105d <+109>: leaq   -0x38(%rbp), %rdi
0x10da91061 <+113>: leaq   -0x20(%rbp), %rdx
0x10da91065 <+117>: callq  *0x180(%rax)
0x10da9106b <+123>: movq   -0x28(%rbp), %rax
0x10da9106f <+127>: movq   %rax, 0x10(%rbx)
0x10da91073 <+131>: movq   -0x38(%rbp), %rax
0x10da91077 <+135>: movq   -0x30(%rbp), %rcx
0x10da9107b <+139>: movq   %rcx, 0x8(%rbx)
0x10da9107f <+143>: movq   %rax, (%rbx)
0x10da91082 <+146>: jmp0x10da91030   ; <+64>
0x10da91084 <+148>: nopw   %cs:(%rax,%rax)

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

[digikam] [Bug 365684] Crash when deleting a tag from the list of tags

[via KDE Bugzilla]

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

--- Comment #8 from caulier.gil...@gmail.com ---
Debuging under OSX is not too simple as Linux or Windows.

I tried, as Windows version, to include GDB, but it prohibited to attached
process to debugger without to sign GDB to Apple service. It's for security
reason (as Apple said).

Alternative is to patch internal settings from OSX and restart it. But it's not
sure that it work with last OSX version.

The most simpler way, is to use a debugger already signed and available in
AppStore.

Here i use XCode, I start digiKam, and i attched the process to Xcode debugger.
There are few command in Xcode menu to use. It's simple. After that, you use
digiKam until it crash. XCode will indicate where process is stopped in code
with the call backtrace.

The problem is that XCode is a huge package to install. I don't yet tried to
check if a small debugger exists in AppStore.

Gilles Caulier

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

[digikam] [Bug 365684] Crash when deleting a tag from the list of tags

[Olli Lupton via KDE Bugzilla]

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

--- Comment #7 from Olli Lupton  ---
Hi,

I just tried as you suggested, re-naming the database files and letting it
rebuild them.

This does not fix the problem. I removed a tag and it crashed again, see below.

Is there another way of running the OS X packaged build in some debug mode that
would provide more useful information?

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

Exception Type:EXC_BAD_ACCESS (SIGSEGV)
Exception Codes:   EXC_I386_GPFLT
Exception Note:EXC_CORPSE_NOTIFY

Global Trace Buffer (reverse chronological seconds):
2867.649195  libextension.dylib0x7fff8bd44533 tearing down
extension request for pid 35499
2877.727496  libextension.dylib0x7fff8bd44533 tearing down
extension request for pid 35499

Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0   org.qt-project.QtCore 0x000113ac7042
QSortFilterProxyModel::parent(QModelIndex const&) const + 82
1   org.qt-project.QtWidgets  0x000112f3e9c7
QTreeView::isIndexHidden(QModelIndex const&) const + 71
2   org.qt-project.QtWidgets  0x000112f32f31
QTreeView::visualRect(QModelIndex const&) const + 97
3   org.qt-project.QtWidgets  0x000112eda8fc
QAccessibleTableCell::rect() const + 44
4   org.qt-project.QtWidgets  0x000112eda6b9
QAccessibleTableCell::state() const + 169
5   libqcocoa.dylib   0x00011d58c6ca
QCocoaAccessible::hasValueAttribute(QAccessibleInterface*) + 58
6   libqcocoa.dylib   0x00011d588e3f
-[QMacAccessibilityElement accessibilityAttributeNames] + 431
7   com.apple.AppKit  0x7fff942c3e1a
NSAccessibilityEntryPointAttributeNames + 124
8   com.apple.AppKit  0x7fff94532552
-[NSObject(NSAccessibilityInternal) _accessibilityAttributeNamesClientError:] +
56
9   com.apple.AppKit  0x7fff94535976 CopyAttributeNames +
216
10  com.apple.HIServices  0x7fff90a1623b
_AXXMIGCopyAttributeNames + 245
11  com.apple.HIServices  0x7fff90a1f823 _XCopyAttributeNames +
367
12  com.apple.HIServices  0x7fff909fa012 mshMIGPerform + 199
13  com.apple.CoreFoundation  0x7fff90275019
__CFRUNLOOP_IS_CALLING_OUT_TO_A_SOURCE1_PERFORM_FUNCTION__ + 41
14  com.apple.CoreFoundation  0x7fff90274f89 __CFRunLoopDoSource1 +
473
15  com.apple.CoreFoundation  0x7fff9026c9bb __CFRunLoopRun + 2171
16  com.apple.CoreFoundation  0x7fff9026bed8 CFRunLoopRunSpecific +
296
17  com.apple.HIToolbox   0x7fff80819935
RunCurrentEventLoopInMode + 235
18  com.apple.HIToolbox   0x7fff8081976f ReceiveNextEventCommon
+ 432
19  com.apple.HIToolbox   0x7fff808195af
_BlockUntilNextEventMatchingListInModeWithFilter + 71
20  com.apple.AppKit  0x7fff940feefa _DPSNextEvent + 1067
21  com.apple.AppKit  0x7fff940fe32a -[NSApplication
_nextEventMatchingEventMask:untilDate:inMode:dequeue:] + 454
22  com.apple.AppKit  0x7fff940f2e84 -[NSApplication run] +
682
23  libqcocoa.dylib   0x00011d57734f
QCocoaEventDispatcher::processEvents(QFlags) +
2191
24  org.qt-project.QtCore 0x000113af43d1
QEventLoop::exec(QFlags) + 417
25  org.qt-project.QtCore 0x000113af8885
QCoreApplication::exec() + 341
26  digikam   0x00010cd0b1dc main + 9084
27  libdyld.dylib 0x7fff871b75ad start + 1

Thread 1:: Dispatch queue: com.apple.libdispatch-manager
0   libsystem_kernel.dylib0x7fff811feefa kevent_qos + 10
1   libdispatch.dylib 0x7fff8e456165 _dispatch_mgr_invoke +
216
2   libdispatch.dylib 0x7fff8e455dcd _dispatch_mgr_thread +
52

Thread 2:: Digikam::ScanController
0   libsystem_kernel.dylib0x7fff811fddb6 __psynch_cvwait + 10
1   libsystem_pthread.dylib   0x7fff80b77728 _pthread_cond_wait +
767
2   org.qt-project.QtCore 0x000113930d0b
QWaitConditionPrivate::wait(unsigned long) + 75
3   org.qt-project.QtCore 0x000113930bc2
QWaitCondition::wait(QMutex*, unsigned long) + 162
4   libdigikamgui.5.0.0.dylib 0x00010cd41d62
Digikam::ScanController::run() + 562
5   org.qt-project.QtCore 0x00011392f6ea
QThreadPrivate::start(void*) + 362
6   libsystem_pthread.dylib   0x7fff80b7699d _pthread_body + 131
7   libsystem_pthread.dylib   0x7fff80b7691a _pthread_start + 168
8   libsystem_pthread.dylib   0x7fff80b74351 thread_start + 13

Thread 3:: com.apple.NSEventThread
0   libsystem_kernel.dylib0x7fff811f7f72 mach_msg_trap + 10
1   libsystem_kernel.dylib0x7fff811f73b3 mach_msg + 55
2   com.apple.CoreFoundation  

[digikam] [Bug 365684] Crash when deleting a tag from the list of tags

[via KDE Bugzilla]

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

--- Comment #6 from caulier.gil...@gmail.com ---
I suspect something wrong with old sqlite  database files.

Please rename these files es *.old, and recreate the database from scratch.

Gilles Caulier

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

[digikam] [Bug 365684] Crash when deleting a tag from the list of tags

[Olli Lupton via KDE Bugzilla]

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

--- Comment #5 from Olli Lupton  ---
Thanks for looking into this!

Database type: SQLite (created with digikam 4.X)
Database location: local SSD
Collection location: local HDD (machine has 1 SSD, 1 HDD)

I ran in a terminal as you suggested. The only output triggered by deleting a
tag is:

digikam.geoiface: 
digikam.geoiface: 
digikam.general: Stacked View Mode :  0
digikam.general: Delete Shortcut assigned to tag  610
digikam.geoiface: 
Segmentation fault: 11

Which doesn't seem that informative to me. In case it helps, here are the first
few lines printed by digikam after startup. Let me know if there's anything
else I can try?

$ /opt/digikam/Applications/KF5/digikam.app/Contents/MacOS/digikam
digikam.general: AlbumWatch use QFileSystemWatcher
QFileSystemWatcher::removePaths: list is empty
digikam.general: Database Parameters:
   Type: "QSQLITE"
   DB Core Name: "/Users/oliver/DigikamDatabases/digikam4.db"
   DB Thumbs Name:  
"/Users/oliver/DigikamDatabases/thumbnails-digikam.db"
   DB Face Name: "/Users/oliver/DigikamDatabases/recognition.db"
   Connect Options:  ""
   Host Name:""
   Host port:-1
   Internal Server:  false
   Internal Server Path: ""
   Internal Server Serv Cmd: ""
   Internal Server Init Cmd: ""
   Username: ""
   Password: ""

digikam.dbengine: Loading SQL code from config file
"/opt/digikam/Applications/KF5/digikam.app/Contents/Resources//digikam/database/dbconfig.xml"
digikam.dbengine: Checking XML version ID => expected:  3  found:  3
digikam.coredb: Core database: running schema update
digikam.coredb: Core database: have a structure version  8
digikam.coredb: Core database: makeUpdates  8  to  8
digikam.database: Creating new Location  "/"  uuid 
"volumeid:?path=/Volumes/Data Disk/Pictures/Photos"
digikam.database: Creating new Location  "/"  uuid 
"volumeid:?path=/Volumes/Data Disk/Pictures/Archive"
digikam.database: location for  "/Volumes/Data Disk/Pictures/Photos"  is
available  true
digikam.database: location for  "/Volumes/Data Disk/Pictures/Archive"  is
available  true
KMemoryInfo: Platform identified :  "Unknown"
KMemoryInfo: TotalRam:  -1
digikam.general: Allowing a cache size of 60 MB
digikam.thumbsdb: ThumbDB SelectThumbnailSetting val ret =  0
digikam.thumbsdb: ThumbDB SelectThumbnailSetting val ret =  0
digikam.thumbsdb: Thumbs database: have a structure version  "3"
digikam.general: Thumbnails database ready for use
digikam.database: Complete scan (file scanning deferred) took: 16711 msecs.

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

[digikam] [Bug 365684] Crash when deleting a tag from the list of tags

[via KDE Bugzilla]

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

--- Comment #4 from caulier.gil...@gmail.com ---
Also which type of database you use ? sqlite or mysql ?

I tried with both and i cannot reproduce the problem...

Gilles Caulier

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

[digikam] [Bug 365684] Crash when deleting a tag from the list of tags

[via KDE Bugzilla]

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

--- Comment #3 from caulier.gil...@gmail.com ---
Note : I cannot reproduce the crash here. I can play with tags in tree view as
well (move, remove, create, rename, etc...)

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

[digikam] [Bug 365684] Crash when deleting a tag from the list of tags

[via KDE Bugzilla]

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

caulier.gil...@gmail.com changed:

   What|Removed |Added

 CC||caulier.gil...@gmail.com

--- Comment #2 from caulier.gil...@gmail.com ---
Which database type do you use ?
Where is stored your database file (in case of Sqlite) ?
Where is stored your collection ?
Can you run digiKam from a console to see all debug statements printed before
to crash ? digiKam executable is installed in
/opt/digikam/Applications/KF5/digikam.app/Contents/MacOS/digikam

Gilles Caulier

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

[digikam] [Bug 365684] Crash when deleting a tag from the list of tags

[Olli Lupton via KDE Bugzilla]

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

--- Comment #1 from Olli Lupton  ---
Two further comments:

1. The operation does seem to succeed (i.e. the tag is removed), despite the
crash.
2. I see a similar crash if, in the tag manager, I try and move a tag (e.g.
SomeName -> People/SomeName).

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