Bug-Report from Application: ktechlab (0.40.1)

[Zoltan Padrah]

Hi,

can you save the circuit (before starting simulation), which makes ktechlab
crash when starting simulation? And send it here or attach it a bug report?
It looks to me that some specific sequence of action makes the internal
model of the circuit go inconsistent, and then the simulation crashes.
Reproducing this crash could be a first step in fixing it.

Best regards,

 Zoltan



Alexander Kaiser <KaiserAk945 at gmx.de> ezt írta (időpont: 2019. aug. 12., H,
16:36):

> Application: ktechlab (0.40.1)
>
> KDE Platform Version: 4.14.16
>
> Qt Version: 4.8.7
>
> Operating System: Linux 4.14.48-041448-generic i686
>
> Distribution: Ubuntu 16.04.6 LTS
>
> -- Information about the crash:
>
> <In detail, tell us what you were doing when the application crashed.>
>
> The program crashed shortly after i started to start "simulation".
>
> In Terminal the last looping messages was "(Critical) ktechlab(9154): Wire
> voltage error: 5" + "(Critical) ktechlab(9154): Wire voltage error:
> 0.790619"...
>
> -- Backtrace:
>
> Application: KTechLab (ktechlab), signal: Segmentation fault
>
> Using host libthread_db library "/lib/i386-linux-gnu/libthread_db.so.1".
>
> [Current thread is 1 (Thread 0xb2ae6800 (LWP 9154))]
>
> Thread 2 (Thread 0xadce0b40 (LWP 9155)):
>
> #0 0xb52a049d in g_mutex_lock () from /lib/i386-linux-gnu/libglib-2.0.so.0
>
> #1 0xb52594a2 in g_main_context_prepare () from
> /lib/i386-linux-gnu/libglib-2.0.so.0
>
> #2 0xb525a024 in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
>
> #3 0xb525a254 in g_main_context_iteration () from
> /lib/i386-linux-gnu/libglib-2.0.so.0
>
> #4 0xb6a9311c in QEventDispatcherGlib::processEvents (this=0xad300470,
> flags=...) at kernel/qeventdispatcher_glib.cpp:452
>
> #5 0xb6a5ec5d in QEventLoop::processEvents (this=0xadce01a4, flags=...) at
> kernel/qeventloop.cpp:149
>
> #6 0xb6a5efee in QEventLoop::exec (this=0xadce01a4, flags=...) at
> kernel/qeventloop.cpp:204
>
> #7 0xb69400eb in QThread::exec (this=0x961a110) at thread/qthread.cpp:538
>
> #8 0xb6a3e4a6 in QInotifyFileSystemWatcherEngine::run (this=0x961a110) at
> io/qfilesystemwatcher_inotify.cpp:265
>
> #9 0xb6942d3e in QThreadPrivate::start (arg=0x961a110) at
> thread/qthread_unix.cpp:352
>
> #10 0xb535e295 in start_thread (arg=0xadce0b40) at pthread_create.c:333
>
> #11 0xb59ed0ae in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:114
>
> Thread 1 (Thread 0xb2ae6800 (LWP 9154)):
>
> [KCrash Handler]
>
> #7 0x080f03ea in LogicIn::callCallback (this=0x96b5690) at
> /home/alexander/TEMP/ktechlab-0.40.1/src/electronics/simulation/logic.h:100
>
> #8 0x080efe61 in Simulator::step (this=0x94172f0) at
> /home/alexander/TEMP/ktechlab-0.40.1/src/simulator.cpp:201
>
> #9 0xb6a75d6b in QMetaObject::activate (sender=0x91eed60, m=0xb6bdf688
> <QTimer::staticMetaObject>, local_signal_index=0, argv=0x0) at
> kernel/qobject.cpp:3567
>
> #10 0xb6acb822 in QTimer::timeout (this=0x91eed60) at
> .moc/release-shared/moc_qtimer.cpp:147
>
> #11 0xb6a8120f in QTimer::timerEvent (this=0x91eed60, e=0xbfbaaebc) at
> kernel/qtimer.cpp:280
>
> #12 0xb6a7bd8e in QObject::event (this=0x91eed60, e=0xbfbaaebc) at
> kernel/qobject.cpp:1253
>
> #13 0xb6d1864a in QApplicationPrivate::notify_helper (this=0x90153d0,
> receiver=0x91eed60, e=0xbfbaaebc) at kernel/qapplication.cpp:4570
>
> #14 0xb6d1f951 in QApplication::notify (this=0xbfbab1a0,
> receiver=0x91eed60, e=0xbfbaaebc) at kernel/qapplication.cpp:4356
>
> #15 0xb61d871c in KApplication::notify(QObject*, QEvent*) () from
> /usr/lib/libkdeui.so.5
>
> #16 0xb6a6057a in QCoreApplication::notifyInternal (this=0xbfbab1a0,
> receiver=0x91eed60, event=0xbfbaaebc) at kernel/qcoreapplication.cpp:955
>
> #17 0xb6a958c9 in QCoreApplication::sendEvent (event=0xbfbaaebc,
> receiver=<optimized out>) at
> ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:231
>
> #18 QTimerInfoList::activateTimers (this=0x901516c) at
> kernel/qeventdispatcher_unix.cpp:621
>
> #19 0xb6a9272c in timerSourceDispatch (source=<optimized out>) at
> kernel/qeventdispatcher_glib.cpp:193
>
> #20 idleTimerSourceDispatch (source=0x90151a0) at
> kernel/qeventdispatcher_glib.cpp:240
>
> #21 0xb5259ee9 in g_main_context_dispatch () from
> /lib/i386-linux-gnu/libglib-2.0.so.0
>
> #22 0xb525a189 in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
>
> #23 0xb525a254 in g_main_context_iteration () from
> /lib/i386-linux-gnu/libglib-2.0.so.0
>
> #24 0xb6a930f5 in QEventDispatcherGlib::processEvents (this=0x8ff0890,
> flags=...) at kernel/qeventdispatcher_glib.cpp:450
>
> #25 0xb6dd5b66 in QGuiEventDispatcherGlib::processEvents (this=0x8ff0890,
> flags=...) at kernel/qguieventdispatcher_glib.cpp:204
>
> #26 0xb6a5ec5d in QEventLoop::processEvents (this=0xbfbab104, flags=...)
> at kernel/qeventloop.cpp:149
>
> #27 0xb6a5efee in QEventLoop::exec (this=0xbfbab104, flags=...) at
> kernel/qeventloop.cpp:204
>
> #28 0xb6a655f6 in QCoreApplication::exec () at
> kernel/qcoreapplication.cpp:1227
>
> #29 0xb6d164e4 in QApplication::exec () at kernel/qapplication.cpp:3828
>
> #30 0x08070101 in main (argc=1, argv=0xbfbab274) at
> /home/alexander/TEMP/ktechlab-0.40.1/src/core/main.cpp:98
>
> Report to ktechlab-devel at kde.org
>
> _______________________________________________
> Ktechlab-devel mailing list
> Ktechlab-devel at kde.org
> https://mail.kde.org/mailman/listinfo/ktechlab-devel
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/ktechlab-devel/attachments/20190812/f400c98d/attachment-0001.html>