Bug 196558 - KTurtle Crash when opening new sample while other sample was running
Summary: KTurtle Crash when opening new sample while other sample was running
Status: RESOLVED WORKSFORME
Alias: None
Product: kturtle
Classification: Applications
Component: general (other bugs)
Version First Reported In: unspecified
Platform: Ubuntu Unspecified
: NOR crash
Target Milestone: ---
Assignee: Cies Breijs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-06-15 03:44 UTC by Petter Vikenes
Modified: 2021-01-16 04:33 UTC (History)
2 users (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Petter Vikenes 2009-06-15 03:44:44 UTC
Version:            (using KDE 4.2.4)
Installed from:    Ubuntu Packages

Application: KTurtle (kturtle), signal SIGABRT
[Current thread is 0 (LWP 22465)]

Thread 2 (Thread 0xaff13b90 (LWP 22691)):
#0  0xb806d430 in __kernel_vsyscall ()
#1  0xb684b7b1 in select () from /lib/tls/i686/cmov/libc.so.6
#2  0xb7f3d380 in ?? () from /usr/lib/libQtCore.so.4
#3  0xb7e6b96e in ?? () from /usr/lib/libQtCore.so.4
#4  0xb667e4ff in start_thread () from /lib/tls/i686/cmov/libpthread.so.0
#5  0xb685349e in clone () from /lib/tls/i686/cmov/libc.so.6

Thread 1 (Thread 0xb609f9f0 (LWP 22465)):
[KCrash Handler]
#6  0xb806d430 in __kernel_vsyscall ()
#7  0xb679a6d0 in raise () from /lib/tls/i686/cmov/libc.so.6
#8  0xb679c098 in abort () from /lib/tls/i686/cmov/libc.so.6
#9  0xb67d824d in ?? () from /lib/tls/i686/cmov/libc.so.6
#10 0xb67de604 in ?? () from /lib/tls/i686/cmov/libc.so.6
#11 0xb67e05b6 in free () from /lib/tls/i686/cmov/libc.so.6
#12 0xb69c0231 in operator delete () from /usr/lib/libstdc++.so.6
#13 0x0807ba75 in _start ()
Comment 1 Cies Breijs 2009-06-15 15:13:31 UTC
ok, i'll fix it... please (niels, anybody) don't fix it as im working in a local branch currently.

fix: grey out opening of anything when 'running'.
Comment 2 Cies Breijs 2009-09-02 12:01:25 UTC
this very serious bug (as it is a crash bug) will get fixed later, at least by me. i comfort myself that it only happens in very rare use case.

i would like to fix this one using the QStateMachine framework in Qt4.6. it is not clear yet if 4.6 feature can be used in kde4.4 (the next release). as soon as 4.6 can be used i'll have a look.

with the state machine we can refactor the code for mainwindow, making it more organized. currently i think of 2 separate state machines:
- for the execution
- for the editing (modification)

thanks for the patience.
Comment 3 José JORGE 2018-10-30 22:49:06 UTC
Was this code reworked? Or maybe this is related to bug 270031?
Comment 4 Justin Zobel 2020-12-17 05:38:27 UTC
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.
Comment 5 Bug Janitor Service 2021-01-01 04:34:13 UTC
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!
Comment 6 Bug Janitor Service 2021-01-16 04:33:49 UTC
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!