Mentions légales du service

Skip to content

Blockly crash (from the thymio forum)

Created by: cbarraud

Hi,

I just transmit a message from Thymio's forum: https://www.thymio.org/forum/t-1982307/blockly-plantage-lors-de-l-utilisation-de-repeter-jusqu-a#post-2685986

Bonjour Ne trouvant pas de forum dédié à blockly, je poste dans celui concernant VPL, pour un crash de l'interface lors de l'utilisation de blockly. Ce comportement a été constaté avec la version 1.5.3 d'AsebaStudio sur 2 ordinateurs différents (un sous Debian testing, l'autre sous Ubuntu). Pour reproduire le bug, il suffit d'essayer de construire une boucle du type "répéter jusqu'à (capteur de sol détecte quelque chose et vrai)" : image

L'interface plante alors avec un SIGABRT. Voici la stacktrace récupérée par le test du bug sous gdb:

Starting program: /usr/bin/asebastudio [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [New Thread 0x7fffe8336700 (LWP 7267)] [New Thread 0x7fffe7b35700 (LWP 7268)] [Thread 0x7fffe8336700 (LWP 7267) exited] [Thread 0x7fffe7b35700 (LWP 7268) exited] [New Thread 0x7fffe7b35700 (LWP 7271)] libpng warning: iCCP: known incorrect sRGB profile libpng warning: iCCP: known incorrect sRGB profile [New Thread 0x7fffe8336700 (LWP 7272)] [New Thread 0x7fffdffff700 (LWP 7273)] [Thread 0x7fffe8336700 (LWP 7272) exited] [Thread 0x7fffdffff700 (LWP 7273) exited] [New Thread 0x7fffdffff700 (LWP 7274)] [New Thread 0x7fffe8336700 (LWP 7275)] [New Thread 0x7fffde7eb700 (LWP 7276)] [New Thread 0x7fff9787b700 (LWP 7281)]

Thread 10 "Thread (pooled)" received signal SIGABRT, Aborted. [Switching to Thread 0x7fff9787b700 (LWP 7281)] __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:58 58 ../sysdeps/unix/sysv/linux/raise.c: Aucun fichier ou dossier de ce type. (gdb) bt #0 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:58 #1 (closed) 0x00007ffff314940a in __GI_abort () at abort.c:89 #2 (closed) 0x000000000053f767 in Aseba::BinaryArithmeticNode::deMorganNotRemoval() () #3 (closed) 0x000000000053fa97 in Aseba::UnaryArithmeticNode::optimize(std::basic_ostream<wchar_t, std::char_traits<wchar_t> >*) () #4 (closed) 0x000000000053fb30 in Aseba::WhileNode::optimize(std::basic_ostream<wchar_t, std::char_traits<wchar_t> >*) () #5 0x000000000053feb4 in Aseba::BlockNode::optimize(std::basic_ostream<wchar_t, std::char_traits<wchar_t> >*) () #6 0x000000000053ff67 in Aseba::IfWhenNode::optimize(std::basic_ostream<wchar_t, std::char_traits<wchar_t> >*) () #7 (closed) 0x000000000053feb4 in Aseba::BlockNode::optimize(std::basic_ostream<wchar_t, std::char_traits<wchar_t> >*) () #8 (closed) 0x0000000000523c73 in Aseba::Compiler::compile(std::basic_istream<wchar_t, std::char_traits<wchar_t> >&, Aseba::BytecodeVector&, unsigned int&, Aseba::Error&, std::basic_ostream<wchar_t, std::char_traits<wchar_t> >*) () #9 (closed) 0x000000000049c157 in Aseba::compilationThread (targetDescription=..., commonDefinitions=..., source=..., dump=dump@entry=true) at /build/aseba-EiRPC2/aseba-1.5.3/clients/studio/MainWindow.cpp:1059 #10 (closed) 0x00000000004b8d74 in QtConcurrent::StoredFunctorCall4<Aseba::NodeTab::CompilationResult*, Aseba::NodeTab::CompilationResult* (*)(Aseba::TargetDescription, Aseba::CommonDefinitions, QString, bool), Aseba::TargetDescription, Aseba::CommonDefinitions, QString, bool>::runFunctor (this=0xf89b90) at /usr/include/qt4/QtCore/qtconcurrentstoredfunctioncall.h:876 #11 (closed) 0x00000000004b3cc5 in QtConcurrent::RunFunctionTaskAseba::NodeTab::CompilationResult*::run ( this=0xf89b90) at /usr/include/qt4/QtCore/qtconcurrentrunbase.h:106 #12 (closed) 0x00007ffff3dbcdba in ?? () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #13 (closed) 0x00007ffff3dc9daa in ?? () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #14 (closed) 0x00007ffff2cf7464 in start_thread (arg=0x7fff9787b700) at pthread_create.c:333 #15 (closed) 0x00007ffff31fd9df in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:105 (gdb)

On my platform (Windows 8.1, Aseba 1.5.3) it crashes also:

image

It's really when you place the sensor (whichever) that it crashes.

I'll put a reference to this issue in the forum.

Christophe