[Ktechlab-devel] Fwd: Re: sdcc problem

[P Zoltan]

   Hi,

  I've just comitted a few changes to the svn:
- fpnode's code cleanup
- some stability fixes

Known bugs:

- an InputFlowNode can be connected to an OutpudFlowNode which is already  
connected (practically more than 1 output connectors are possbile for any  
flowpart :\ )


  I'm forwarding a bug report because it's of general interest:

------- Forwarded message -------
From: "Luis Claudio Gamboa Lopes" <lcgamboa at yahoo.com>
To: "P Zoltan" <zoltan.padrah at gmail.com>
Cc:
Subject: Re: [Ktechlab-devel] sdcc problem
Date: Thu, 25 Sep 2008 03:26:00 +0200

Hi Zoltan,

>>  Does the newest svn version of ktechlab crash when closing a tab?
Yes

>>  If it does, please write down exactly how to reproduce it.

In the sdcc_test (or other c file), if the pic in circuit is running and  
the code is open in other tab, close the code tab crash the program.

Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread -1247365440 (LWP 4960)]
[KCrash handler]
#9  0xb6bf7ab2 in KXMLGUIClient::factory () from /usr/lib/libkdeui.so.4
#10 0x08119da9 in TextView::~TextView ()
#11 0xb6331a4b in QWidget::~QWidget () from /usr/lib/libqt-mt.so.3
#12 0xb63b5f07 in QFrame::~QFrame () from /usr/lib/libqt-mt.so.3
#13 0xb64391cb in QSplitter::~QSplitter () from /usr/lib/libqt-mt.so.3
#14 0x0813c871 in ViewArea::~ViewArea ()
#15 0xb62f441e in QObject::event () from /usr/lib/libqt-mt.so.3
#16 0xb632b612 in QWidget::event () from /usr/lib/libqt-mt.so.3
#17 0xb64382e5 in QSplitter::event () from /usr/lib/libqt-mt.so.3
#18 0xb628cc26 in QApplication::internalNotify () from  
/usr/lib/libqt-mt.so.3
#19 0xb628f5d6 in QApplication::notify () from /usr/lib/libqt-mt.so.3
#20 0xb6a3de0e in KApplication::notify () from /usr/lib/libkdecore.so.4
#21 0xb6220421 in QApplication::sendEvent () from /usr/lib/libqt-mt.so.3
#22 0xb628dc4e in QApplication::sendPostedEvents ()
    from /usr/lib/libqt-mt.so.3
#23 0xb628dd56 in QApplication::sendPostedEvents ()
    from /usr/lib/libqt-mt.so.3
#24 0xb6233d6f in QEventLoop::processEvents () from /usr/lib/libqt-mt.so.3
#25 0xb62a7179 in QEventLoop::enterLoop () from /usr/lib/libqt-mt.so.3
#26 0xb62a6f9a in QEventLoop::exec () from /usr/lib/libqt-mt.so.3
#27 0xb628e7bf in QApplication::exec () from /usr/lib/libqt-mt.so.3
#28 0x08179361 in main ()



>>  Finally: how should I reproduce the .asm problem? With latest svn, I
>> could convert it to hex and I could simulate that program.

Open ktechlab, create a new circuit, put an pic on it, load the shift.asm  
an programa crash! Ktecklab run gpasm and shift.hex is created, but on  
load the program crash!

Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread -1247160640 (LWP 5078)]
[KCrash handler]
#9  0xb663ba1b in QString::QString () from /usr/lib/libqt-mt.so.3
#10 0x081e9ae2 in PICComponent::slotCODCreationSucceeded ()
#11 0x081e9dcc in PICComponent::qt_invoke ()
#12 0xb6326d4f in QObject::activate_signal () from /usr/lib/libqt-mt.so.3
#13 0xb63277e0 in QObject::activate_signal () from /usr/lib/libqt-mt.so.3
#14 0x082e5e2a in ProcessChain::successful ()
#15 0x082e6eb0 in ProcessChain::slotFinishedCompile ()
#16 0x082e9672 in ProcessChain::qt_invoke ()
#17 0xb6326d4f in QObject::activate_signal () from /usr/lib/libqt-mt.so.3
#18 0x082e179e in Language::processSucceeded ()
#19 0x082e3c4a in Language::finish ()
#20 0x083000b2 in ExternalLanguage::processExited ()
#21 0x083006c2 in ExternalLanguage::qt_invoke ()
#22 0xb6326d4f in QObject::activate_signal () from /usr/lib/libqt-mt.so.3
#23 0xb699a081 in KProcess::processExited () from /usr/lib/libkdecore.so.4
#24 0xb699a2af in KProcess::processHasExited () from  
/usr/lib/libkdecore.so.4
#25 0xb6995540 in KProcessController::slotDoHousekeeping ()
    from /usr/lib/libkdecore.so.4
#26 0xb6995652 in KProcessController::qt_invoke ()
    from /usr/lib/libkdecore.so.4
#27 0xb6326d4f in QObject::activate_signal () from /usr/lib/libqt-mt.so.3
#28 0xb6327656 in QObject::activate_signal () from /usr/lib/libqt-mt.so.3
#29 0xb66b0957 in QSocketNotifier::activated () from /usr/lib/libqt-mt.so.3
#30 0xb63494fa in QSocketNotifier::event () from /usr/lib/libqt-mt.so.3
#31 0xb62bec26 in QApplication::internalNotify () from  
/usr/lib/libqt-mt.so.3
#32 0xb62c0a43 in QApplication::notify () from /usr/lib/libqt-mt.so.3
#33 0xb6a6fe0e in KApplication::notify () from /usr/lib/libkdecore.so.4
#34 0xb6252421 in QApplication::sendEvent () from /usr/lib/libqt-mt.so.3
#35 0xb62b0fd9 in QEventLoop::activateSocketNotifiers ()
    from /usr/lib/libqt-mt.so.3
#36 0xb6266754 in QEventLoop::processEvents () from /usr/lib/libqt-mt.so.3
#37 0xb62d9179 in QEventLoop::enterLoop () from /usr/lib/libqt-mt.so.3
#38 0xb62d8f9a in QEventLoop::exec () from /usr/lib/libqt-mt.so.3
#39 0xb62c07bf in QApplication::exec () from /usr/lib/libqt-mt.so.3
#40 0x08179361 in main ()

I'm using
Linux debian 2.6.18 #4 SMP Tue Aug 12 11:47:22 BRT 2008 i686 GNU/Linux
gpasm-0.13.6 beta
gpsim-version: Release 0.22.0
sdcc-2.8.0 #5117 (Jun  6 2008)

Prof.Luis Claudio Gambôa Lopes



  The second bug is hopefully fixed by a semi-hack in rev 146. The big  
problem is that Ktechlab cannot detect the type of the PIC from the  
source-code file.

   Zoltan