Ceedling icon indicating copy to clipboard operation
Ceedling copied to clipboard

Test executable failed: Bad Memory - Ceedling not receiving stdout

Open beckerzito opened this issue 4 years ago • 1 comments

Hi folks,

In my company, we used to have the tests running using the MinGW32 distribution for Windows. Once this distribution had its support ended and due to other limitations of GCC configuration that wasn't passing the command line file, '@file' option, to the assembler, breaking the compilation process, we decided to move for CYGWIN64 distribution.

In the first moment, the transition seemed to work, when all the tests passed. However, I just realized that if any test fails for any reason, ceedling fails with the "Bad memory access issue", as you can see below:

image

I know that it might be related to the software execution being broken due to some wrong memory access, such as pointer not initialized, as in many other issues in this forum.

However, what is weird to me, is that if I run the .out isolated, I'm able to get the output for all the tests, see below: image

But even though it's returning the outputs, ceedling is getting empty value in the returned value from the fixture task.

Have anyone faced this issue before? Am I missing some configuration that might be related to the different GCC distributions? It's important to note that I changed from i686 arch (MinGW32) to x86_64 (CYGWIN32).

beckerzito avatar Jul 07 '21 13:07 beckerzito

Did you ever find a solution?

MadsLundJensen avatar Sep 04 '23 07:09 MadsLundJensen