I do not understand this error

Simulide 0.4.15 with some patterns when I start the simulation comes out, it does it only certain times especially when it has just been started.
Debugging gives me this error but I can't attribute it to a component.
It would seem arduino and the serial, however, I do not understand.
What the following error can be caused by.



Greetings

I can't see nothing there.
What is the problem?
Does simulide crash at that line?

Simulide closes "simulator.cpp line 164".
If you open the image you see the whole screen.
Greetings

Ok, then you need to see what is "el", and that is not shown in the image.

Probably whatever "el" is, it was deleted and didn't remove itself from simuclock list.

If I first open another scheme and then open the one that gives the error if opened first, it works.
Greetings

Is there some element that is added to simuclock and then deleted without removing from simuclock?

I copied and pasted the schematic into a new one but the same error happens.
From the debug it seems that initially in the clock list there are 2 elements and when i2c starts they become 3 from here one creates the error.



If I delete the speaker the simulation works and the debug is this:

0x1a2a548
eElement "baseprocessor"
0x1a2a548
eElement "baseprocessor"
0x1a2a548
eElement "baseprocessor"
0x1a2a548
eElement "baseprocessor"
0x1a2a548
eElement "baseprocessor"
0x1a2a548
eElement "baseprocessor"
0x1a2a548
eElement "baseprocessor"
AvrCompBase::twenChanged Enable: 1
AvrCompBase::twenChanged i2cFreq: 100000
0x1a2a548
eElement "baseprocessor"
0x1a2a640
eElement "avrI2C"
0x1a2a548
eElement "baseprocessor"
0x1a2a640
eElement "avrI2C"
0x1a2a548
eElement "baseprocessor"
0x1a2a640
eElement "avrI2C"
0x1a2a548
eElement "baseprocessor"
0x1a2a640
eElement "avrI2C"

Greetings

I can't reproduce the issue.

Which version or revision of 0.4.15 are you using?
Did you do some modifications?

Also if you share your circuit I can test it.

Simulide 0.4.15 271

It is working for me, no crashes.
Is there something I have to do to reproduce the issue?

I don't know I'm unlucky.
How can I check if the "el" pointer is valid?
What causes the error I get when I start Simulide 0.4.15
271 from Qt creator:

: -1: error: [Makefile: 2046: runLrelease] Error 1

Greetings

How can I check if the "el" pointer is valid?

It is not valid because the program crash when you call it.

What causes the error I get when I start Simulide 0.4.15
271 from Qt creator:

: -1: error: [Makefile: 2046: runLrelease] Error 1

I don't know, runLrelease has not changed for a long time.

I think you should do a clean build.
make clean, and delete all files in the build folder except .pro and .pro.user.
Then run qmake and build.

I meant a way to make this condition but it doesn't work like this:

if (el) el->simuClockStep();

Greetings

I meant a way to make this condition but it doesn't work like this:

if (el) el->simuClockStep();

No, that only works if "el" is NULL.

I did like this:

Code:


if( !m_simuClock.isEmpty() )          // Run elements at Simulation Clock
 {
            for( eElement* el : m_simuClock ) {
                if (m_simuClock.contains(el))
                    el->simuClockStep();
            }
 }


it is strange but Simulide no longer closes.
Greetings

Another error that happened to me, when after an undo I started the simulation in complex schemes Simulide crashed, was solved in a similar way.

On these "for" Qt creator gives the following warning :

waring
C++ 11 range-loop might detach Qt container (QList) [clazy-range-loop]

Here it is solved like this row 120 and 323:

Code:


    for( eElement* el : m_updateList ) {
      if (m_elementList.contains(el))
          el->updateStep();
    }


Greetings

Another error that happened to me, when after an undo I started the simulation in complex schemes Simulide crashed, was solved in a similar way.

That's a good clue.

In Simulide 0.4.15 I corrected this function:

Code:


void KY023::remove()
{
    delete m_sw;              // This line was missing
    delete m_vrx;
    delete m_vry;
    Component::remove();
}


Now it no longer crashes.
In version 1.0.0 it still sometimes comes out with UNDO.
But I still don't understand what it depends on.
Greetings

In Simulide 0.4.15 I corrected this function:

Thanks, change done at Rev 272.