Bug 70262 - crash in picture classification dialog
Summary: crash in picture classification dialog
Status: RESOLVED FIXED
Alias: None
Product: kimdaba
Classification: Unmaintained
Component: general (show other bugs)
Version: unspecified
Platform: Gentoo Packages Linux
: NOR crash
Target Milestone: ---
Assignee: Jesper K. Pedersen
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-12-13 01:05 UTC by Dominik Stadler
Modified: 2003-12-13 13:56 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments
Valgrind-Output of starting KimDaBa and producing the crash (9.12 KB, text/plain)
2003-12-13 13:24 UTC, Dominik Stadler
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Dominik Stadler 2003-12-13 01:05:42 UTC
Version:           1.0.1 (using KDE KDE 3.1.4)
Installed from:    Gentoo Packages
Compiler:          gcc 3.3.2 
OS:          Linux

I get repeated crashes in the dialog where I attach strings to the images. It happens not always at the same place and the crash-report below does not provide much information, but I can reproduce it quite consitently.

This happens at various places in the dialog. Sometimes when I do a right-click somewhere, sometimes when I try to drag around one of the drop-in-windows, ... 

This is quite annoying, because when I try to classify a huge collection of images, it happens every now and then and I have to restart, reorganize the windows and start working where the last auto-save left off.

(no debugging symbols found)...Using host libthread_db library "/lib/libthread_db.so.1".
(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...[Thread debugging using libthread_db enabled]
[New Thread 16384 (LWP 21451)]
[New Thread 32769 (LWP 23284)]
[New Thread 16386 (LWP 23285)]

0x4106f03b in waitpid () from /lib/libpthread.so.0
#0  0x4106f03b in waitpid () from /lib/libpthread.so.0
#1  0x406ebc94 in __JCR_LIST__ () from /usr/kde/3.1/lib/libkdecore.so.4
Comment 1 Jesper Pedersen 2003-12-13 09:39:06 UTC
Subject: Re:  New: crash in picture classification dialog

Dominik Stadler <dominik.stadler@gmx.at> writes:

| ------- You are receiving this mail because: -------
| You are the assignee for the bug, or are watching the assignee.
|      
| http://bugs.kde.org/show_bug.cgi?id=70262     
|            Summary: crash in picture classification dialog
|            Product: kimdaba
|            Version: unspecified
|           Platform: Gentoo Packages
|         OS/Version: Linux
|             Status: UNCONFIRMED
|           Severity: crash
|           Priority: NOR
|          Component: general
|         AssignedTo: blackie@blackie.dk
|         ReportedBy: dominik.stadler@gmx.at
| 
| 
| Version:           1.0.1 (using KDE KDE 3.1.4)
| Installed from:    Gentoo Packages
| Compiler:          gcc 3.3.2 
| OS:          Linux
| 
| I get repeated crashes in the dialog where I attach strings to the images. It happens not always at the same place and the crash-report below does not provide much information, but I can reproduce it quite consitently.
| 
| This happens at various places in the dialog. Sometimes when I do a right-click somewhere, sometimes when I try to drag around one of the drop-in-windows, ... 
| 
| This is quite annoying, because when I try to classify a huge collection of images, it happens every now and then and I have to restart, reorganize the windows and start working where the last auto-save left off.
| 
| (no debugging symbols found)...Using host libthread_db library "/lib/libthread_db.so.1".
| (no debugging symbols found)...
| (no debugging symbols found)...(no debugging symbols found)...
| (no debugging symbols found)...(no debugging symbols found)...
| (no debugging symbols found)...(no debugging symbols found)...
| (no debugging symbols found)...(no debugging symbols found)...
| (no debugging symbols found)...(no debugging symbols found)...
| (no debugging symbols found)...(no debugging symbols found)...
| (no debugging symbols found)...(no debugging symbols found)...[Thread debugging using libthread_db enabled]
| [New Thread 16384 (LWP 21451)]
| [New Thread 32769 (LWP 23284)]
| [New Thread 16386 (LWP 23285)]
| 
| 0x4106f03b in waitpid () from /lib/libpthread.so.0
| #0  0x4106f03b in waitpid () from /lib/libpthread.so.0
| #1  0x406ebc94 in __JCR_LIST__ () from /usr/kde/3.1/lib/libkdecore.so.4
Could you try running the program through valgrind.
If you don't have it installed you can download it from 
http://valgrind.kde.org/

compiling it is nothing but ./configure; make; make install

now run it as: valgrind --num-callers=100 kimdaba
and send me the output when you've made kimdaba crash.

Thanks
Jesper.

Comment 2 Dominik Stadler 2003-12-13 13:24:44 UTC
Created attachment 3677 [details]
Valgrind-Output of starting KimDaBa and producing the crash
Comment 3 Dominik Stadler 2003-12-13 13:41:42 UTC
The easiest way to reproduce this is now to:

1. Open KimDaBa
2. Open some images
3. Right click on the image and show the dialog
4. Resize the dialog somewhat
5. Do a right-click in one of the list-boxes

This consistently crashes KimDaBa.
Comment 4 Jesper Pedersen 2003-12-13 13:49:33 UTC
I've tried valgrinding kimdaba for a long time now dragging windows around 
etc, but without a single error message.

looking at your valgrind outout it indicates to me that the error is not in kimdaba code but rather in KDockWindow code, which would also explain why I dont see any errors (I'm using KDE Head, while you are likely using a 
KDE 3.1.x version.

If you are using KDE HEAD, please let me know, otherwise I'm afraid there is not much I can do.

Cheers
Jesper.

PS: You might want to save your current window setup (from the menu you get in by pressing the "Options..." button), just in case the error only shows up when moving windows around.
Comment 5 Jesper Pedersen 2003-12-13 13:50:43 UTC
I did manage to reproduce the other part of your bug report, which I do believe is unrelated - I'm looking at it now.
Comment 6 Jesper Pedersen 2003-12-13 13:56:40 UTC
Yup that was indeed a bug.
You clicked outside any items, and that makes kimdaba crash
I've fixed this in CVS now.

Thanks.