Bug 178690 - ADEPT, sources can not be read
Summary: ADEPT, sources can not be read
Status: RESOLVED DUPLICATE of bug 175540
Alias: None
Product: adept
Classification: Miscellaneous
Component: general (show other bugs)
Version: unspecified
Platform: Ubuntu Linux
: NOR normal
Target Milestone: ---
Assignee: Peter Rockai
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-12-24 19:57 UTC by Rob
Modified: 2009-01-18 20:50 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Rob 2008-12-24 19:57:19 UTC
Version:            (using KDE 4.1.3)
OS:                Linux
Installed from:    Ubuntu Packages

Application: Adept (adept), signal SIGABRT
(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 0xb5e5e8d0 (LWP 6029)]
[New Thread 0xb472cb90 (LWP 6037)]
(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)
(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)
(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)
[KCrash handler]
#6  0xb7f30430 in __kernel_vsyscall ()
#7  0xb66ef880 in raise () from /lib/tls/i686/cmov/libc.so.6
#8  0xb66f1248 in abort () from /lib/tls/i686/cmov/libc.so.6
#9  0xb69136f8 in __gnu_cxx::__verbose_terminate_handler ()
   from /usr/lib/libstdc++.so.6
#10 0xb69115d5 in ?? () from /usr/lib/libstdc++.so.6
#11 0xb6911612 in std::terminate () from /usr/lib/libstdc++.so.6
#12 0xb69116cb in __cxa_rethrow () from /usr/lib/libstdc++.so.6
#13 0xb73a4de5 in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#14 0xb73a57e2 in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#15 0xb73aadb7 in ?? () from /usr/lib/libQtCore.so.4
#16 0xb73aaedc in ?? () from /usr/lib/libQtCore.so.4
#17 0xb739f53f in QObject::event () from /usr/lib/libQtCore.so.4
#18 0xb6a808ec in QApplicationPrivate::notify_helper ()
   from /usr/lib/libQtGui.so.4
#19 0xb6a8872e in QApplication::notify () from /usr/lib/libQtGui.so.4
#20 0xb785fb2d in KApplication::notify () from /usr/lib/libkdeui.so.5
#21 0xb738fe61 in QCoreApplication::notifyInternal ()
   from /usr/lib/libQtCore.so.4
#22 0xb73bdd81 in ?? () from /usr/lib/libQtCore.so.4
#23 0xb73ba520 in ?? () from /usr/lib/libQtCore.so.4
#24 0xb61d66f8 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#25 0xb61d9da3 in ?? () from /usr/lib/libglib-2.0.so.0
#26 0xb61d9f61 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#27 0xb73ba478 in QEventDispatcherGlib::processEvents ()
   from /usr/lib/libQtCore.so.4
#28 0xb6b1aea5 in ?? () from /usr/lib/libQtGui.so.4
#29 0xb738e52a in QEventLoop::processEvents () from /usr/lib/libQtCore.so.4
#30 0xb738e6ea in QEventLoop::exec () from /usr/lib/libQtCore.so.4
#31 0xb7390da5 in QCoreApplication::exec () from /usr/lib/libQtCore.so.4
#32 0xb6a80767 in QApplication::exec () from /usr/lib/libQtGui.so.4
#33 0x080c80c6 in ?? ()
#34 0xb66da685 in __libc_start_main () from /lib/tls/i686/cmov/libc.so.6
#35 0x08095ae1 in _start ()
#0  0xb7f30430 in __kernel_vsyscall ()


That is the output. Had not been in Adept in days..no ideas what might cause this. Anyone else know about this??!!
Comment 1 FiNeX 2008-12-25 16:56:10 UTC
Hi! If you can reproduce the crash, you should install the debug enabled packages and provide a new backtrace. Read this page for the instructions:

http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports

Thanks!
Comment 2 Jonathan Thomas 2009-01-18 20:50:27 UTC

*** This bug has been marked as a duplicate of bug 175540 ***