User Activity

  • Posted a comment on discussion Free Support on QP actor frameworks and QM modeling tool

    Good point. The QP/Spy functionality has been vastly extended in the latest QP/C/C++ releses and the documentation still needs to catch up with these developments. So, an example cross-reference will be added in the future to the QP/C/C++ Reference Manuals. For now, I'd like to point you to the following QP/Spy examples: examples\qutest - examples for the QUTest unit testing harness examples\arm-cm\dpp_efm32-slstk3401a - QSpyView examples for the EFM32 board examples\arm-cm\dpp_ek-tm4c123gxl - QSpyView...

  • Committed [37ffba]

    5.9.3

  • Committed [0bc7cf]

    5.9.3

  • Posted a comment on discussion Free Support on QP actor frameworks and QM modeling tool

    This sounds like a reasonable request. We'll look into this for the future QP/C/C++ releases. For now I just captured this as a feature request #126 Allow non-asserting event allocation for zero-margin allocations. --MMS

  • Created ticket #126 on QP actor frameworks and QM modeling tool

    Allow non-asserting event allocation for zero-margin allocations

  • Modified a comment on discussion Free Support on QP actor frameworks and QM modeling tool

    Manu: this is probably urelated to your corrupted event pool assertions. But in your screen shot you apparently send a pointer to a data buffer me->SestinatinData.pData inside an event. In most cases this is a bad idea, because the external data buffer is a shared resource. So, by putting a pointer to this shared buffer you bypass all safety mechanisms in the framework to deliver event data in a thread-safe manner from the producer to the consumer. Sure, the framework delivers the pointer correctly,...

  • Modified a comment on discussion Free Support on QP actor frameworks and QM modeling tool

    Manu: this is probably urelated to your corrupted event pool assertions. But in your screen shot you apparently send a pointer to data buffer me->SestinatinData.pData inside an event. In most cases this is a bad idea, because the external data buffer is a shared resource. So, by putting a pointer to this shared buffer you bypass all safety mechanisms in the framework to deliver event data in a thread-safe manner from the producer to the consumer. Sure, the framework delivers the pointer correctly,...

  • Posted a comment on discussion Free Support on QP actor frameworks and QM modeling tool

    Manu: this is probably urelated to your corrupted event pool assertions. But in your screen shot you apparently send a pointer to data buffer me->SestinatinData.pData inside an event. In most cases this is a bad idea, because the external data buffer is a shared resource. So, by putting a pointer to this shared buffer you bypass all safety mechanisms in the framework to deliver event data in a thread-safe manner from the producer to the consumer. Sure, the framework delivers the pointer correctly,...

View All

Personal Data

Username:
quantum-leaps
Joined:
2005-01-13 16:41:55

Projects

Skills

  • No skills entered.

Personal Tools

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:

JavaScript is required for this form.





No, thanks