On 2019-12-08 19:19, Thiago Macieira wrote:
On Sunday, 8 December 2019 00:35:04 PST Ramakanth Kesireddy wrote:
Something is very wrong. Check this assertion and fix:0: error:
Deallocating non-allocated memory
allocated at file: line: 0 size: 0 type: unknown
deallocated at file:
On Sunday, 8 December 2019 00:35:04 PST Ramakanth Kesireddy wrote:
> Something is very wrong. Check this assertion and fix:0: error:
> Deallocating non-allocated memory
>allocated at file: line: 0 size: 0 type: unknown
>deallocated at file: line: 0 type: delete
>
> Main to run qt u
Thanks it works.
However, it gives generic failure rather than specific failure in the test
when used with Qt.
unknown file:0: error: Failure in TEST(
NOTE: Assertion happened without being in a test run (perhaps in main?),
Something is very wrong. Check this assertion and fix)
Somet
On Fri, 6 Dec 2019 08:23:20 +0530
Ramakanth Kesireddy wrote:
> When unit test binary(using cpputest to run the testcases + QTest for the
> specific Qt functionality)is executed on embedded target(linux), it doesnot
> shows any test summary/results with respect to number of testcases run on
> cons
Hi,
When unit test binary(using cpputest to run the testcases + QTest for the
specific Qt functionality)is executed on embedded target(linux), it doesnot
shows any test summary/results with respect to number of testcases run on
console.
There is no issue when it is run on Ubuntu linux.
Whether Q
