| Summary: | Kturtle crashes sometimes when lauching a script | ||
|---|---|---|---|
| Product: | [Applications] kturtle | Reporter: | José JORGE <lists.jjorge> |
| Component: | general | Assignee: | Cies Breijs <cies> |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | crash | CC: | int.teo, nielsslot, vitorboschi |
| Priority: | NOR | ||
| Version First Reported In: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | Mageia RPMs | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
| Attachments: | The testcase file | ||
|
Description
José JORGE
2011-04-03 22:10:05 UTC
Can you tell me if you were creating and using functions ('learn') in your scripts?
Also, if it's not too much trouble, could you please also include the script that caused the crash?
Created attachment 58562 [details]
The testcase file
Yes, I use the learn function. Here is a script that crashes often.
Yep, indeed. If you try executing this script 3-4 times, it eventually crashes. Here is my backtrace and it seems to be related to bug #269806 Application: KTurtle (kturtle), signal: Segmentation fault [Current thread is 1 (Thread 0xb41a3710 (LWP 3274))] Thread 2 (Thread 0xb0fd0b70 (LWP 3275)): #0 0xb5d85296 in clock_gettime (clock_id=1, tp=0xb0fcffa0) at ../sysdeps/unix/clock_gettime.c:100 #1 0xb765d079 in do_gettime () at tools/qelapsedtimer_unix.cpp:123 #2 qt_gettime () at tools/qelapsedtimer_unix.cpp:140 #3 0xb7734df6 in QTimerInfoList::updateCurrentTime (this=0x96925b4) at kernel/qeventdispatcher_unix.cpp:339 #4 0xb7734e3a in QTimerInfoList::timerWait (this=0x96925b4, tm=...) at kernel/qeventdispatcher_unix.cpp:442 #5 0xb7732e40 in timerSourcePrepareHelper (src=<value optimized out>, timeout=0xb0fd00bc) at kernel/qeventdispatcher_glib.cpp:136 #6 0xb7732edd in timerSourcePrepare (source=0x0, timeout=0xb5d88ff4) at kernel/qeventdispatcher_glib.cpp:169 #7 0xb5cd03d1 in g_main_context_prepare (context=0x9873728, priority=0xb0fd013c) at gmain.c:2469 #8 0xb5cd07f1 in g_main_context_iterate (context=0x9873728, block=<value optimized out>, dispatch=1, self=0x9873318) at gmain.c:2760 #9 0xb5cd0de9 in g_main_context_iteration (context=0x9873728, may_block=1) at gmain.c:2843 #10 0xb7732c0f in QEventDispatcherGlib::processEvents (this=0x9870980, flags=...) at kernel/qeventdispatcher_glib.cpp:424 #11 0xb770279a in QEventLoop::processEvents (this=0xb0fd0290, flags=) at kernel/qeventloop.cpp:149 #12 0xb7702c1a in QEventLoop::exec (this=0xb0fd0290, flags=...) at kernel/qeventloop.cpp:201 #13 0xb75fe8df in QThread::exec (this=0x9691e88) at thread/qthread.cpp:492 #14 0xb76e155c in QInotifyFileSystemWatcherEngine::run (this=0x9691e88) at io/qfilesystemwatcher_inotify.cpp:248 #15 0xb7601bf3 in QThreadPrivate::start (arg=0x9691e88) at thread/qthread_unix.cpp:320 #16 0xb755bcf3 in start_thread (arg=0xb0fd0b70) at pthread_create.c:301 #17 0xb5e5e6be in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:133 Thread 1 (Thread 0xb41a3710 (LWP 3274)): [KCrash Handler] #7 deref (this=0x9764258, tree=0x99a92e8, _errorList=0x97643c8) at /usr/include/qt4/QtCore/qatomic_i386.h:132 #8 ~QHash (this=0x9764258, tree=0x99a92e8, _errorList=0x97643c8) at /usr/include/qt4/QtCore/qhash.h:284 #9 Executer::initialize (this=0x9764258, tree=0x99a92e8, _errorList=0x97643c8) at /var/tmp/portage/kde-base/kturtle-4.6.1/work/kturtle-4.6.1/kturtle/src/interpreter/executer.cpp:66 #10 0x0808af0a in Interpreter::interpret (this=0x97787d8) at /var/tmp/portage/kde-base/kturtle-4.6.1/work/kturtle-4.6.1/kturtle/src/interpreter/interpreter.cpp:95 #11 0x0807f9cd in MainWindow::qt_metacall (this=0x96ad1a8, _c=QMetaObject::InvokeMetaMethod, _id=0, _a=0xbfdf21ec) at /var/tmp/portage/kde-base/kturtle-4.6.1/work/kturtle-4.6.1_build/kturtle/src/mainwindow.moc:215 #12 0xb7709b7a in QMetaObject::metacall (object=0x96ad1a8, cl=158745192, idx=65, argv=0xbfdf21ec) at kernel/qmetaobject.cpp:237 #13 0xb771cb17 in QMetaObject::activate (sender=0x977b518, m=0xb78355a4, local_signal_index=0, argv=0x0) at kernel/qobject.cpp:3278 #14 0xb776ebe8 in QTimer::timeout (this=0x977b518) at .moc/release-shared/moc_qtimer.cpp:134 #15 0xb772279e in QTimer::timerEvent (this=0x977b518, e=0xbfdf272c) at kernel/qtimer.cpp:271 #16 0xb771682c in QObject::event (this=0x977b518, e=0x1) at kernel/qobject.cpp:1181 #17 0xb6bd9bd4 in QApplicationPrivate::notify_helper (this=0x9497c88, receiver=0x977b518, e=0xbfdf272c) at kernel/qapplication.cpp:4462 #18 0xb6bdec6e in QApplication::notify (this=0xbfdf2ac0, receiver=0x977b518, e=0xbfdf272c) at kernel/qapplication.cpp:3862 #19 0xb65a278b in KApplication::notify (this=0xbfdf2ac0, receiver=0x977b518, event=0xbfdf272c) at /var/tmp/portage/kde-base/kdelibs-4.6.1-r1/work/kdelibs-4.6.1/kdeui/kernel/kapplication.cpp:311 #20 0xb7703d32 in QCoreApplication::notifyInternal (this=0xbfdf2ac0, receiver=0x977b518, event=0xbfdf272c) at kernel/qcoreapplication.cpp:731 #21 0xb773635f in sendEvent (this=0x949a97c) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:215 #22 QTimerInfoList::activateTimers (this=0x949a97c) at kernel/qeventdispatcher_unix.cpp:604 #23 0xb7732f48 in timerSourceDispatch (source=0x949a9b0) at kernel/qeventdispatcher_glib.cpp:184 #24 idleTimerSourceDispatch (source=0x949a9b0) at kernel/qeventdispatcher_glib.cpp:231 #25 0xb5cccc7c in g_main_dispatch (context=0x949a090) at gmain.c:2149 #26 g_main_context_dispatch (context=0x949a090) at gmain.c:2702 #27 0xb5cd0bf8 in g_main_context_iterate (context=0x949a090, block=<value optimized out>, dispatch=1, self=0x9497850) at gmain.c:2780 #28 0xb5cd0de9 in g_main_context_iteration (context=0x949a090, may_block=1) at gmain.c:2843 #29 0xb7732bc6 in QEventDispatcherGlib::processEvents (this=0x9481be8, flags=...) at kernel/qeventdispatcher_glib.cpp:422 #30 0xb6c9ab96 in QGuiEventDispatcherGlib::processEvents (this=0x9481be8, flags=...) at kernel/qguieventdispatcher_glib.cpp:204 #31 0xb770279a in QEventLoop::processEvents (this=0xbfdf29f4, flags=) at kernel/qeventloop.cpp:149 #32 0xb7702c1a in QEventLoop::exec (this=0xbfdf29f4, flags=...) at kernel/qeventloop.cpp:201 #33 0xb7707271 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1008 #34 0xb6bd82f8 in QApplication::exec () at kernel/qapplication.cpp:3736 #35 0x08071f54 in main (argc=5, argv=0xbfdf2d64) at /var/tmp/portage/kde-base/kturtle-4.6.1/work/kturtle-4.6.1/kturtle/src/main.cpp:84 Bug still there with KDE 4.6.2 But stil there with KDE 4.8.5 (Mageia 2) Dear Bug Submitter, This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond. Thank you for helping us make KDE software even better for everyone! Still reproductible :open in khotnewstuff 2 scripts, it always crash with "Hole or summit" opened in second place. Thank you for the crash report. As it has been a while since this was reported, can you please test and confirm if this issue is still occurring or if this bug report can be marked as resolved. I have set the bug status to "needsinfo" pending your response, please change back to "reported" or "resolved/worksforme" when you respond, thank you. Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! |