Bug 292611 - cantor is crashing with scilab backend enable
Summary: cantor is crashing with scilab backend enable
Status: RESOLVED FIXED
Alias: None
Product: cantor
Classification: Applications
Component: scilab-backend (show other bugs)
Version: 0.3
Platform: Mageia RPMs Linux
: NOR crash
Target Milestone: ---
Assignee: Alexander Rieder
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-01-27 17:25 UTC by Balcaen John
Modified: 2016-04-02 22:56 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 Balcaen John 2012-01-27 17:25:24 UTC
Application: cantor (0.3)
KDE Platform Version: 4.8.00 (4.8.0
Qt Version: 4.8.0
Operating System: Linux 3.2.1-desktop-2.mga2 x86_64
Distribution: "Mageia Cauldron"

-- Information about the crash:
- What I was doing when the application crashed:
I simply start cantor, once i select scilab backend , cantor is crashing on every start
scliab version is 5.3.3

The crash can be reproduced every time.

-- Backtrace:
Application: Cantor (cantor), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
82	T_PSEUDO (SYSCALL_SYMBOL, SYSCALL_NAME, SYSCALL_NARGS)
[KCrash Handler]
#6  Cantor::Expression::setResult (this=0x35323d6c616d726f, result=0xfc8940) at /usr/src/debug/cantor-4.8.0/src/lib/expression.cpp:109
#7  0x00007f07a34bce60 in ScilabExpression::parseError (this=0x35323d6c616d726f, error=...) at /usr/src/debug/cantor-4.8.0/src/backends/scilab/scilabexpression.cpp:107
#8  0x00007f07a34bafdb in ScilabSession::readError (this=0xf2f3a0) at /usr/src/debug/cantor-4.8.0/src/backends/scilab/scilabsession.cpp:181
#9  0x00007f07a34bc39d in ScilabSession::qt_static_metacall (_o=<optimized out>, _c=<optimized out>, _id=<optimized out>, _a=<optimized out>) at /usr/src/debug/cantor-4.8.0/build/src/backends/scilab/scilabsession.moc:57
#10 0x00007f07b2a5d871 in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () from /usr/lib64/libQtCore.so.4
#11 0x00007f07b29e60bb in QProcessPrivate::_q_canReadStandardError() () from /usr/lib64/libQtCore.so.4
#12 0x00007f07b29e6f4e in QProcess::qt_static_metacall(QObject*, QMetaObject::Call, int, void**) () from /usr/lib64/libQtCore.so.4
#13 0x00007f07b2a5d871 in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () from /usr/lib64/libQtCore.so.4
#14 0x00007f07b2aaa52e in QSocketNotifier::activated(int) () from /usr/lib64/libQtCore.so.4
#15 0x00007f07b2a66b2b in QSocketNotifier::event(QEvent*) () from /usr/lib64/libQtCore.so.4
#16 0x00007f07b340fa74 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib64/libQtGui.so.4
#17 0x00007f07b34148f3 in QApplication::notify(QObject*, QEvent*) () from /usr/lib64/libQtGui.so.4
#18 0x00007f07b4e43736 in KApplication::notify (this=0x7fffaddeeef0, receiver=0xe2b9a0, event=0x7fffaddeec70) at /usr/src/debug/kdelibs-4.8.0/kdeui/kernel/kapplication.cpp:311
#19 0x00007f07b2a49cbc in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib64/libQtCore.so.4
#20 0x00007f07b2a77f87 in socketNotifierSourceDispatch(_GSource*, int (*)(void*), void*) () from /usr/lib64/libQtCore.so.4
#21 0x00007f07aed905ba in g_main_dispatch (context=0xb89020) at gmain.c:2513
#22 g_main_context_dispatch (context=0xb89020) at gmain.c:3050
#23 0x00007f07aed90980 in g_main_context_iterate (dispatch=1, block=<optimized out>, context=0xb89020, self=<optimized out>) at gmain.c:3121
#24 g_main_context_iterate (context=0xb89020, block=<optimized out>, dispatch=1, self=<optimized out>) at gmain.c:3058
#25 0x00007f07aed90a44 in g_main_context_iteration (context=0xb89020, may_block=1) at gmain.c:3182
#26 0x00007f07b2a788bf in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQtCore.so.4
#27 0x00007f07b34b25fe in QGuiEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQtGui.so.4
#28 0x00007f07b2a48aa2 in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQtCore.so.4
#29 0x00007f07b2a48cf7 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQtCore.so.4
#30 0x00007f07b2a4d7e5 in QCoreApplication::exec() () from /usr/lib64/libQtCore.so.4
#31 0x000000000040a457 in main (argc=1, argv=0x7fffaddef288) at /usr/src/debug/cantor-4.8.0/src/main.cpp:87

Reported using DrKonqi
Comment 1 Filipe Saraiva 2012-01-28 17:44:02 UTC
Hi,

I am the developer of this backend.

Scilab backend require Scilab 5.4 version, but to use other version no crash Cantor, only the backend no works properly.

The Scilab backend compiled from KDE repository is ok, no crash.

Is possible other KDE developers test this bug in your respective Linux distributions?

Thanks.
Comment 2 Filipe Saraiva 2012-02-01 00:09:01 UTC
HI,

I and some friends did tests with Cantor and Scilab in some Linux and FreeBSD distributions.

This bug, really, is a Cantor bug.

Apparently, Scilab emit a error message without any command input in Scilab workspace. Its crash Cantor.

The last messages when launch Cantor by konsole:

----
cantor(5641) ScilabSession::readError: readError
cantor(5641) ScilabSession::readError: error:  "Gtk-Message: Failed to load module "canberra-gtk-module"
"
cantor(5641) ScilabExpression::parseError: error "Gtk-Message: Failed to load module "canberra-gtk-module"
"
KCrash: Application 'cantor' crashing...
KCrash: Attempting to start /usr/lib/kde4/libexec/drkonqi from kdeinit
sock_file=/home/filipe/.kde4/socket-localhost/kdeinit4__0
---

In some tests, other messages were released, but always error messages.

I will work in this bug to Cantor backend works properly in KDE 4.8.1.

Thanks,
Comment 3 Filipe Saraiva 2012-02-29 21:38:27 UTC
Hi Balcaen,

I can't did reproduce this bug with Cantor compiled from repository, but I worked in a fix based on messages after crash.

Let's test it with KDE 4.8.1.

Thanks,
Comment 4 Filipe Saraiva 2012-03-09 09:53:01 UTC
Really fixed in KDE 4.8.1.
Working fine in Mageia Cauldron.
Thanks,