Recent changes to bugs

[Build Error]: CUNIT build error for arm-none-eabi-gcc toolchain

Anonymous — Tue, 16 Feb 2021 08:31:31 -0000

Hi,

I am using Cunit testing framework for NXP project using arm-none-eabi-gcc compiler, i was able to use Cuint library for C/C++ projects in NXP S32DS IDE, but i am getting lots of error for NXP's S32DS project (arm-none-eabi-gcc) i have added headers, library and library path to project build settings.

and the error are as follows

make -j4 all 
Building target: Test_Arm.elf
Invoking: Standard S32DS C Linker
arm-none-eabi-gcc -o "Test_Arm.elf" "@Test_Arm.args"  
./src/testC.o: In function `main':
C:\CUNIT_DIR\Test_Arm\Test_Arm\Debug_FLASH/../src/testC.c:18: undefined reference to `CU_initialize_registry'
C:\CUNIT_DIR\Test_Arm\Test_Arm\Debug_FLASH/../src/testC.c:26: undefined reference to `CU_basic_set_mode'
C:\CUNIT_DIR\Test_Arm\Test_Arm\Debug_FLASH/../src/testC.c:28: undefined reference to `CU_set_error_action'
C:\CUNIT_DIR\Test_Arm\Test_Arm\Debug_FLASH/../src/testC.c:31: undefined reference to `CU_basic_run_tests'
C:\CUNIT_DIR\Test_Arm\Test_Arm\Debug_FLASH/../src/testC.c:33: undefined reference to `CU_cleanup_registry'
./src/testsource.o: In function `test_Subtract':
C:\CUNIT_DIR\Test_Arm\Test_Arm\Debug_FLASH/../src/testsource.c:26: undefined reference to `CU_assertImplementation'
./src/testsource.o: In function `test_Add_02':
C:\CUNIT_DIR\Test_Arm\Test_Arm\Debug_FLASH/../src/testsource.c:19: undefined reference to `CU_assertImplementation'
./src/testsource.o: In function `test_Add_01':
C:\CUNIT_DIR\Test_Arm\Test_Arm\Debug_FLASH/../src/testsource.c:14: undefined reference to `CU_assertImplementation'
./src/testsource.o: In function `AddTests':
C:\CUNIT_DIR\Test_Arm\Test_Arm\Debug_FLASH/../src/testsource.c:47: undefined reference to `CU_get_registry'
C:\CUNIT_DIR\Test_Arm\Test_Arm\Debug_FLASH/../src/testsource.c:49: undefined reference to `CU_is_test_running'
C:\CUNIT_DIR\Test_Arm\Test_Arm\Debug_FLASH/../src/testsource.c:51: undefined reference to `CU_register_suites'
C:\CUNIT_DIR\Test_Arm\Test_Arm\Debug_FLASH/../src/testsource.c:53: undefined reference to `CU_get_error_msg'
collect2.exe: error: ld returned 1 exit status
make: *** [makefile:42: Test_Arm.elf] Error 1

Kindly let me what is wrong here with arm compiler

and one more important doubt i have is "is this cunit library will support arm-noneeabi-gcc compiler?"

Thanks in advance

#75 CU_assertImplementation's return value is NOT used

Ian Norton — Wed, 12 Feb 2020 07:42:25 -0000

Hi, I've never seen this warning before.

CUnit now lives at https://gitlab.com/cunity/cunit

#76 Automated.h contains invalid prototype in gcc strict prototype mode

Ian Norton — Wed, 12 Feb 2020 07:37:13 -0000

Hi there, CUnit is now maintained over on gitlab at https://gitlab.com/cunity/cunit and there has been significant work in this area

#76 Automated.h contains invalid prototype in gcc strict prototype mode

M6KVM — Thu, 09 Jan 2020 14:07:02 -0000

Our reference: AST-3754

Automated.h contains invalid prototype in gcc strict prototype mode

M6KVM — Thu, 09 Jan 2020 14:05:10 -0000

The prototype for the function CU_automated_package_name_get() in CUnit/Headers/Automated.h is incomplete because it is declared as () rather than (void).

This causes a problem with the gcc compiler flag -Wstrict-prototypes is used.
Patch supplied.

CU_assertImplementation's return value is NOT used

wangyushui — Thu, 10 Oct 2019 09:23:45 -0000

function 'CU_assertImplementation ' has return value，but it is used by CU_ASSERT_EQUAL without return value judge

#define CU_ASSERT_EQUAL(actual, expected) \
  { CU_assertImplementation(((actual) == (expected)), __LINE__, ("CU_ASSERT_EQUAL(" #actual "," #expected ")"), __FILE__, "", CU_FALSE); }

void testcase_001() 
{
    CU_ASSERT_EQUAL(1, 2);//** there is pclint warning: ignoring return value of function **
}

#70 Inactive test shows as active on test listing

Ian Norton — Fri, 17 May 2019 17:24:30 -0000

This is a duplicate of #74

#74 wrong fActive flag used in Automated.c L708

Ian Norton — Fri, 17 May 2019 17:13:43 -0000

Many thanks, I have logged this over in Gitlab as https://gitlab.com/cunity/cunit/issues/25

wrong fActive flag used in Automated.c L708

Anonymous — Mon, 19 Nov 2018 13:50:03 -0000

Trying to inactivate some tests I realized that they still were displayed as "active" in xml output listing, despite correctly removed from run batch.
IMHO the issue is that pSuite->fActive is used instead of pTest->fActive on Automated.c L708.
Not sure if this was already filed somewhere.

#69 Function pointers cannot be asserted by PTR macros in pedantic, ANSI C

Ian Norton — Thu, 09 Aug 2018 20:51:29 -0000

Migrated to https://gitlab.com/cunity/cunit/issues/4