[Bug 299940] New: crash kfind

caViator caviator.pl at gmail.com
Sun May 13 14:57:46 BST 2012


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

            Bug ID: 299940
          Severity: crash
           Version: 2.0
          Priority: NOR
          Assignee: unassigned-bugs at kde.org
           Summary: crash kfind
    Classification: Unclassified
                OS: Linux
          Reporter: caviator.pl at gmail.com
          Hardware: Ubuntu Packages
            Status: UNCONFIRMED
         Component: general
           Product: kfind

Application: kfind (2.0)
KDE Platform Version: 4.8.3 (4.8.3)
Qt Version: 4.8.1
Operating System: Linux 3.2.0-24-generic i686
Distribution: Ubuntu 12.04 LTS

-- Information about the crash:
- What I was doing when the application crashed:
When you search the contents of the text search kfind suddenly crashed.

The crash can be reproduced every time.

-- Backtrace:
Application: KFind (kfind), signal: Aborted
Using host libthread_db library "/lib/i386-linux-gnu/libthread_db.so.1".
[KCrash Handler]
#7  0x00ef5416 in __kernel_vsyscall ()
#8  0x007c51ef in raise () from /lib/i386-linux-gnu/libc.so.6
#9  0x007c8835 in abort () from /lib/i386-linux-gnu/libc.so.6
#10 0x0060013d in __gnu_cxx::__verbose_terminate_handler() () from
/usr/lib/i386-linux-gnu/libstdc++.so.6
#11 0x005fded3 in ?? () from /usr/lib/i386-linux-gnu/libstdc++.so.6
#12 0x005fdf0f in std::terminate() () from
/usr/lib/i386-linux-gnu/libstdc++.so.6
#13 0x005fe0b4 in __cxa_rethrow () from /usr/lib/i386-linux-gnu/libstdc++.so.6
#14 0x01b45a55 in QEventLoop::exec (this=0xbf974630, flags=...) at
kernel/qeventloop.cpp:218
#15 0x015830c9 in QDialog::exec (this=0xbf9746bc) at dialogs/qdialog.cpp:554
#16 0x080579fb in main (argc=<error reading variable: Cannot access memory at
address 0x2898>, argv=<error reading variable: Cannot access memory at address
0x289c>) at ../../kfind/main.cpp:74

Possible duplicates by query: bug 299281, bug 297850, bug 297620, bug 297169,
bug 297149.

Reported using DrKonqi

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



More information about the Unassigned-bugs mailing list