Here are the last couple of frames from a QPCPP application, before segfaulting. Thread 2 "main" received signal SIGSEGV, Segmentation fault. [Switching to Thread 0x7ffff7e36700 (LWP 12172)] 0x000000000045e284 in QP::QMPool::get (this=0xee8b88 <qp::qf_pool_+40>, margin=0) at qpcpp/src/qf/qf_mem.cpp:235 235 void * const fb_next = fb->m_next; (gdb) backtrace</qp::qf_pool_+40> 0 0x000000000045e284 in QP::QMPool::get (this=0xee8b88 <qp::qf_pool_+40>, margin=0)</qp::qf_pool_+40> at qpcpp/src/qf/qf_mem.cpp:235...
QPCPP : 6.8.0 Target : x86 PC Port : posix-quitest I have implemented an init test similar to the example given under test_table directory in dpp example. It is working fine. But when I try a complex command, I get the following result. QUTest unit testing front-end 6.8.1 running on Python 2.7.17 Copyright (c) 2005-2020 Quantum Leaps, www.state-machine.com Attaching to QSPY (localhost:7701) ... OK Group: test_hall.py Test #0 : Init: Empty Test Setup Empty Teardown PASS (0.014s) Test #1 : Request...
While I agree that it is not easy to change a printed book, it may not be as difficult to change an e-Book. On the other hand, the online manual provides only so much information (compared to the original book), and it is not in a linear format. A linear format, like followed in the PSiCC2 book, is the best way for a beginner to learn and understand the concepts, and easy for an advanced user to brush up topics. My suggestion is to convert the online manual into a book's format, and provide an API...
In the book, qp_port.h is shown in examples as the starting point, and in newer example, I see qpcpp.h as the base header. What was the change about, and which one to be used? Thanks.