Bug 283216 - Evaluation crash
Summary: Evaluation crash
Status: RESOLVED FIXED
Alias: None
Product: cantor
Classification: Applications
Component: sage-backend (show other bugs)
Version: 0.2
Platform: Ubuntu Linux
: NOR crash
Target Milestone: ---
Assignee: Filipe Saraiva
URL:
Keywords: investigated, triaged
: 337851 (view as bug list)
Depends on:
Blocks:
 
Reported: 2011-10-03 02:20 UTC by nooniensoong97
Modified: 2018-09-19 14:37 UTC (History)
4 users (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description nooniensoong97 2011-10-03 02:20:17 UTC
Application: cantor (0.2)
KDE Platform Version: 4.5.5 (KDE 4.5.5)
Qt Version: 4.7.0
Operating System: Linux 2.6.35-30-generic i686
Distribution: Ubuntu 10.10

-- Information about the crash:
- What I was doing when the application crashed:
I was evaluating a sage notebook on Cantor when it crashed. The note book included contour plots of Bessel functions.

The crash can be reproduced some of the time.

-- Backtrace:
Application: Cantor (cantor), signal: Segmentation fault
[Current thread is 1 (Thread 0xb786baa0 (LWP 2962))]

Thread 2 (Thread 0xb74efb70 (LWP 2963)):
#0  0x00e4d416 in __kernel_vsyscall ()
#1  0x00957df6 in poll () from /lib/libc.so.6
#2  0x04294a1b in g_poll () from /lib/libglib-2.0.so.0
#3  0x0428743c in ?? () from /lib/libglib-2.0.so.0
#4  0x04287ba7 in g_main_loop_run () from /lib/libglib-2.0.so.0
#5  0x03a879c4 in ?? () from /usr/lib/libgio-2.0.so.0
#6  0x042ae48f in ?? () from /lib/libglib-2.0.so.0
#7  0x00388cc9 in start_thread () from /lib/libpthread.so.0
#8  0x0096669e in clone () from /lib/libc.so.6

Thread 1 (Thread 0xb786baa0 (LWP 2962)):
[KCrash Handler]
#7  QString::operator= (this=0x40, other=...) at tools/qstring.cpp:1324
#8  0x0830112b in SageExpression::addFileResult (this=0x30, path=...) at ../../../../../cantor/src/backends/sage/sageexpression.cpp:167
#9  0x082fe2bc in SageSession::fileCreated (this=0x92387b0, path=...) at ../../../../../cantor/src/backends/sage/sagesession.cpp:275
#10 0x083005ad in SageSession::qt_metacall (this=0x92387b0, _c=QMetaObject::InvokeMetaMethod, _id=12, _a=0xbfa7c8a8) at ./sagesession.moc:90
#11 0x0216b8ca in QMetaObject::metacall (object=0x92387b0, cl=QMetaObject::ReadProperty, idx=12, argv=0xbfa7c8a8) at kernel/qmetaobject.cpp:237
#12 0x0217e6ad in QMetaObject::activate (sender=0x92387cc, m=0x1b95644, local_signal_index=1, argv=0x9288c00) at kernel/qobject.cpp:3280
#13 0x019f9973 in KDirWatch::created (this=0x92387cc, _t1=...) at ./kdirwatch.moc:106
#14 0x019fa2c4 in KDirWatch::setCreated (this=0x92387cc, _file=...) at ../../kdecore/io/kdirwatch.cpp:1855
#15 0x019fa415 in KDirWatch::qt_metacall (this=0x92387cc, _c=QMetaObject::InvokeMetaMethod, _id=7, _a=0x91e6010) at ./kdirwatch.moc:85
#16 0x0216b8ca in QMetaObject::metacall (object=0x92387cc, cl=QMetaObject::ReadProperty, idx=7, argv=0x91e6010) at kernel/qmetaobject.cpp:237
#17 0x02176df6 in QMetaCallEvent::placeMetaCall (this=0x93277f8, object=0x92387cc) at kernel/qobject.cpp:534
#18 0x021786a2 in QObject::event (this=0x92387cc, e=0x8f14c01) at kernel/qobject.cpp:1219
#19 0x00f79fdc in QApplicationPrivate::notify_helper (this=0x8dce900, receiver=0x92387cc, e=0x93277f8) at kernel/qapplication.cpp:4396
#20 0x00f8004e in QApplication::notify (this=0xbfa7d1e8, receiver=0x92387cc, e=0x93277f8) at kernel/qapplication.cpp:3798
#21 0x005c9d8a in KApplication::notify (this=0xbfa7d1e8, receiver=0x92387cc, event=0x93277f8) at ../../kdeui/kernel/kapplication.cpp:310
#22 0x02165b3b in QCoreApplication::notifyInternal (this=0xbfa7d1e8, receiver=0x92387cc, event=0x93277f8) at kernel/qcoreapplication.cpp:732
#23 0x02168d8b in sendEvent (receiver=0x0, event_type=0, data=0x8db9e98) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:215
#24 QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0, data=0x8db9e98) at kernel/qcoreapplication.cpp:1373
#25 0x02168f4d in QCoreApplication::sendPostedEvents (receiver=0x0, event_type=0) at kernel/qcoreapplication.cpp:1266
#26 0x02194a74 in sendPostedEvents (s=0x8dd0d10) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:220
#27 postEventSourceDispatch (s=0x8dd0d10) at kernel/qeventdispatcher_glib.cpp:277
#28 0x04283855 in g_main_context_dispatch () from /lib/libglib-2.0.so.0
#29 0x04287668 in ?? () from /lib/libglib-2.0.so.0
#30 0x04287848 in g_main_context_iteration () from /lib/libglib-2.0.so.0
#31 0x02194565 in QEventDispatcherGlib::processEvents (this=0x8db9b58, flags=...) at kernel/qeventdispatcher_glib.cpp:415
#32 0x0103bbe5 in QGuiEventDispatcherGlib::processEvents (this=0x8db9b58, flags=...) at kernel/qguieventdispatcher_glib.cpp:204
#33 0x02164609 in QEventLoop::processEvents (this=0xbfa7d144, flags=) at kernel/qeventloop.cpp:149
#34 0x02164a8a in QEventLoop::exec (this=0xbfa7d144, flags=...) at kernel/qeventloop.cpp:201
#35 0x0216900f in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1009
#36 0x00f78e07 in QApplication::exec () at kernel/qapplication.cpp:3672
#37 0x0804f9e7 in main (argc=5, argv=0xbfa7d354) at ../../../cantor/src/main.cpp:86

Reported using DrKonqi
Comment 1 Martin 2012-09-23 23:18:52 UTC
Can you provide us with additional information for this crash? The exact commands you executed would be great, for example. (Or you could compile the current git version of Cantor and try that yourself. Chances are that the bug is fixed there)
Comment 2 Christoph Feck 2014-08-02 19:26:14 UTC
*** Bug 337851 has been marked as a duplicate of this bug. ***
Comment 3 Filipe Saraiva 2016-05-27 18:05:01 UTC
H(In reply to Martin from comment #1)
> Can you provide us with additional information for this crash? The exact
> commands you executed would be great, for example. (Or you could compile the
> current git version of Cantor and try that yourself. Chances are that the
> bug is fixed there)

+1

I am marking this bug as NEEDSINFO, if someone to provide more info I will can to work on it properly.
Comment 4 Andrew Crouthamel 2018-09-19 14:37:30 UTC
This bug has had its resolution changed, but accidentally has been left in NEEDSINFO status. I am thus closing this bug and setting the status as RESOLVED to reflect the resolution change.