[Bug 295670] yet another test
    George Kiagiadakis 
    kiagiadakis.george at gmail.com
       
    Sat Mar 10 12:41:25 GMT 2012
    
    
  
https://bugs.kde.org/show_bug.cgi?id=295670
--- Comment #1 from George Kiagiadakis <kiagiadakis.george at gmail.com> ---
Created attachment 69451
  --> https://bugs.kde.org/attachment.cgi?id=69451&action=edit
New crash information added by DrKonqi
crashtest (1.1) on KDE Platform 4.8.1 (4.8.1) using Qt 4.8.1
- What I was doing when the application crashed:
testing attach to bug report using drkonqi
-- Backtrace (Reduced):
#4  printf (__fmt=0x403d44 "result = %d\n") at /usr/include/bits/stdio2.h:105
#5  do_crash () at
/safe/code/upstream/kde/kde-runtime/drkonqi/tests/crashtest/crashtest.cpp:50
#6  0x0000000000402d71 in level3 (t=<optimized out>) at
/safe/code/upstream/kde/kde-runtime/drkonqi/tests/crashtest/crashtest.cpp:108
#7  level2 (t=<optimized out>) at
/safe/code/upstream/kde/kde-runtime/drkonqi/tests/crashtest/crashtest.cpp:113
#8  level1 (t=<optimized out>) at
/safe/code/upstream/kde/kde-runtime/drkonqi/tests/crashtest/crashtest.cpp:118
--- Comment #2 from George Kiagiadakis <kiagiadakis.george at gmail.com> ---
Created attachment 69452
  --> https://bugs.kde.org/attachment.cgi?id=69452&action=edit
New crash information added by DrKonqi
crashtest (1.1) on KDE Platform 4.8.1 (4.8.1) using Qt 4.8.1
- What I was doing when the application crashed:
testing attach to bug report using drkonqi
-- Backtrace (Reduced):
#4  printf (__fmt=0x403d44 "result = %d\n") at /usr/include/bits/stdio2.h:105
#5  do_crash () at
/safe/code/upstream/kde/kde-runtime/drkonqi/tests/crashtest/crashtest.cpp:50
#6  0x0000000000402d71 in level3 (t=<optimized out>) at
/safe/code/upstream/kde/kde-runtime/drkonqi/tests/crashtest/crashtest.cpp:108
#7  level2 (t=<optimized out>) at
/safe/code/upstream/kde/kde-runtime/drkonqi/tests/crashtest/crashtest.cpp:113
#8  level1 (t=<optimized out>) at
/safe/code/upstream/kde/kde-runtime/drkonqi/tests/crashtest/crashtest.cpp:118
-- 
You are receiving this mail because:
You are the assignee for the bug.
    
    
More information about the Unassigned-bugs
mailing list