Trying to Use Criterion with My Main Function #526

lordmichael95 · 2024-03-13T22:49:56Z

lordmichael95
Mar 13, 2024

Hello All,

I am trying to use Criterion with my main function. To begin with, I can successfully run Criterion tests on my Ubuntu machine when I do not declare my own main function and instead use Criterion’s. However, I have reached the point where I would like to use my own main function and then call Criterion’s tests.

The documentation helpfully provides an example main to show how to accomplish this (https://criterion.readthedocs.io/en/master/internal.html#example-main). However, Criterion ends up throwing some pretty catastrophic errors before core dumping when I use it in conjunction with my set of Criterion tests (this last part is important). When I compile and run my code without the file where I have all my Criterion tests defined (Michaels_Criterion_tests.c) while using my own main.c everything is perfectly happy (Criterion will report zero tests run, zero tests passed, and zero tests failed --- this makes sense, I did not give it any test functions). When I compile and run my code without main.c (and use Criterion’s default behavior), my eight Criterion tests will run, correctly producing four passing and four failing tests. Oddly, it is when I compile and run my code with both main.c and Michaels_Criterion_tests.c where Criterion throws catastrophic errors before core dumping. See output:

./productionProgram 

Hello, World!

The 5th number of the Fibonacci Sequence = 5
The 6th number of the Fibonacci Sequence = 8
The 7th number of the Fibonacci Sequence = 13
criterion: Re-entering criterion from a test worker. This is a catastrophic bug, please report it on the issue tracker.
Bailing out to avoid fork-bombing the system.
criterion: Could not spawn test instance: Protocol error
Aborted (core dumped)

The core file does not seem to actually get created either.

When I am using my own main function, do I need to format the Criterion test file (Michaels_Criterion_tests.c) differently then when I let Criterion use its own main function? Something else?

Below is all the code that I am using:

makefile:

#To build the test files:
#make BUILD_TYPE=test
#To build the production files:
#make
#To generate Doxygen documentation:
#make doc
#To get rid of all object and production executable files:
#make clean


#Compiler command - gcc for C; g++ for C++
CC = gcc
#Compiler flags
CFLAGS = -Wall -Wextra -g
#Location of the Criterion library
LDFLAGS = -L~/Documents/code/Criterion/include
#Name/Linking to the Criterion library
LDLIBS = -lcriterion

#Doxygen configuration filename. Defualt name is: Doxyfile
DOX_CONFIG = Doxyfile

#Source files
#PRODUCTION_SRCS = main.c fibonacci.c
PRODUCTION_SRCS = main.c fibonacci.c Michaels_Criterion_tests.c		###If Michaels_Criterion_tests.c is not compiled along with main.c, Criterion will be fine
TEST_SRCS = Michaels_Criterion_tests.c fibonacci.c

#If BUILD_TYPE = "test", use test files; else, use production files
ifeq ($(BUILD_TYPE), test)
    SRCS = $(TEST_SRCS)
    TARGET = testProgram
else
    SRCS = $(PRODUCTION_SRCS)
    TARGET = productionProgram
endif

#Object files
OBJS = $(SRCS:.c=.o)

#Specifies that "all", "clean", and "doc" are not actual files or folders
.PHONY: all clean doc

all: $(TARGET)

$(TARGET): $(OBJS)
	$(CC) $(CFLAGS) $(LDFLAGS) -o $@ $^ $(LDLIBS)

%.o: %.c
	$(CC) $(CFLAGS) -c -o $@ $<

clean:
	$(RM) $(OBJS) $(TARGET)

#Doxygen documentation generation
doc:
	doxygen $(DOX_CONFIG)

main.c:

#include <stdio.h>
#include <stdlib.h>
#include <criterion/criterion.h>        //Part of Criterion Library
#include "fibonacci.h"

//For unit testing using the Criterion Framework
//If UNIT_TESTING = 0, we are NOT unit testing
//If UNIT_TESTING = 1, we are unit testing
#define UNIT_TESTING 1



/*********************************************************************************************************** 
 * This is the main function. When not unit testing, this is the start of the program. When unit testing
 * Criterion will - by default - use its own main function. Therefore, do not have this file compile when
 * unit testing.
***********************************************************************************************************/ 
int main(int argc, char *argv[]) {
    int holder = 0;         //Holds return values

#if (UNIT_TESTING == 1)     
    //Needed by Criterion. Generates the test set.
    struct criterion_test_set *tests = criterion_initialize();
#endif

    printf("\nHello, World!\n\n");

    //Getting some values of the Fibonacci Sequence
    holder = fib(5);
    printf("The 5th number of the Fibonacci Sequence = %d\n", holder);

    holder = fib(6);
    printf("The 6th number of the Fibonacci Sequence = %d\n", holder);

    holder = fib(7);
    printf("The 7th number of the Fibonacci Sequence = %d\n", holder);

#if (UNIT_TESTING == 1)     
    //Needed by Criterion. Handles all default command-line arguments. Then runs all Criterion tests.
    if (criterion_handle_args(argc, argv, true)){
        criterion_run_all_tests(tests);
    }
#endif    

#if (UNIT_TESTING == 1)     
    //Needed by Criterion. Frees any resources initialized by Criterion.
    criterion_finalize(tests);
#endif
    
    return 0;
}

fibonacci.c

#include "fibonacci.h"

/***********************************************************************************************************
* This function gives the answer of the Fibonacci Sequence. 
*     @param fibSequenceNumber (int) - The nth number of Fibonacci Sequence that you wish to calculate.
*     @return (int) - This is the nth number of Fibonacci Sequence.
************************************************************************************************************/
int fib(int fibSequenceNumber) {
    int answer = 0, b = 1;
    for (int index = 0; index < fibSequenceNumber; index++) {
        int tmp = b;
        b = b + answer;
        answer = tmp;
    }
    return answer;
}

fibonacci.h

#ifndef FIBONACCI_H
#define FIBONACCI

//Function declarations
int fib(int fibSequenceNumber);

#endif /* FIBONACCI_H */

Michaels_Criterion_tests.c

#include <stdio.h>
#include <stdlib.h>
#include <signal.h>
#include "/home/mlayman/Documents/code/Criterion/include/criterion/criterion.h"            //For Criterion framework
#include "/home/mlayman/Documents/code/Criterion/include/criterion/new/assert.h"
#include "Michaels_Criterion_tests.h"
#include "fibonacci.h"

//#define SIGUSR1 56          //re-define User Signal 1

/***********************************************************************************************************
* Information about classes/structs can also be listed. Dummy demo description.
* 
************************************************************************************************************/
struct structOfSignals { 
    int sig50; ///Do I see this??
    int sig51; 
    int sig52; 
}; 


///@brief testValue (int) - This is a global variable used solely for some tests. Does not exist in 
///procduction code.
int testValue;
struct structOfSignals sigs;

/***********************************************************************************************************
 This is how one defines a simple setup function in Criterion. This function will run prior to the 
 test. A message is printed and the variable testValue is assigned the value of 5.
 @param N/A
 @return N/A
************************************************************************************************************/
void setup1(void) {
    puts("setup1: Runs before the test");

    testValue = 5;
}

/***********************************************************************************************************
 This is how one defines a simple teardown function in Criterion. This function will run after the test. 
 A message is printed once the particular test finishes. 
 @param N/A
 @return N/A
************************************************************************************************************/
void teardown(void) {
    puts("Runs after the test");
}

/***********************************************************************************************************
 This is how one defines a simple setup function in Criterion. This function will run prior to the 
 test. A message is printed and the variable testValue is assigned the value of 4.
 @param N/A
 @return N/A
************************************************************************************************************/
void setup2(void) {
    puts("setup2: Runs before the test");

    testValue = 4;
}

/***********************************************************************************************************
 This is how one defines a simple setup function in Criterion. This function will run prior to the 
 test. A message is printed and the variable testValue is assigned the value of 6.
 @param N/A
 @return N/A
************************************************************************************************************/
void setup3(void) {
    puts("setup3: Runs before the test");

    testValue = 6;
}

/***********************************************************************************************************
 In this Criterion test, we are testing if 5 equals 5. Since this is always true, this test should always
 pass.
 @param suite1 (string) - The name of your testing suite. May be any alphanumeric string.
 @param test1 (string) - The name of your test. May be any alphanumeric string.
************************************************************************************************************/
Test(suite1, test1) {
    cr_expect(eq(int, 5, 5));         //Should always pass; 5 = 5
}

/***********************************************************************************************************
 In this Criterion test, we are testing if 4 equals 5. Since this is always false, this test should always
 fail.
 @param suite1 (string) - The name of your testing suite. May be any alphanumeric string.
 @param test2 (string) - The name of your test. May be any alphanumeric string.
************************************************************************************************************/
Test(suite1, test2) {
    cr_expect(eq(int, 4, 5));         //Should always fail; 4 = 5
}

/***********************************************************************************************************
 In this Criterion test, we are testing if 5 equals 5. Since this is always true, this test should always
 pass.
 @param suite1 (string) - The name of your testing suite. May be any alphanumeric string.
 @param test3 (string) - The name of your test. May be any alphanumeric string.
 @param .init (function) - [optional] Pass in the name of your setup function. Function must be defined.
 @param .fini (function) - [optional] Pass in the name of your teardown function. Function must be defined. 
************************************************************************************************************/
Test(suite1, test3, .init = setup1, .fini = teardown) {
    cr_expect(eq(int, testValue, 5));         //Should always pass; 5 = 5
}

/***********************************************************************************************************
 In this Criterion test, we are testing if 4 equals 5. Since this is always false, this test should always
 fail.
 @param suite1 (string) - The name of your testing suite. May be any alphanumeric string.
 @param test4 (string) - The name of your test. May be any alphanumeric string.
 @param .init (function) - [optional] Pass in the name of your setup function. Function must be defined.
 @param .fini (function) - [optional] Pass in the name of your teardown function. Function must be defined. 
************************************************************************************************************/
Test(suite1, test4, .init = setup2, .fini = teardown) {
    cr_expect(eq(int, testValue, 5));         //Should always fail; 4 = 5
}

/***********************************************************************************************************
 In this Criterion test, we are testing if the fifth Fibonacci Sequence 5 equals 5. Since this is always true, 
 this test should always pass.
 @param suite2 (string) - The name of your testing suite. May be any alphanumeric string.
 @param fibonacci1 (string) - The name of your test. May be any alphanumeric string.
************************************************************************************************************/
Test(suite2, fibonacci1) {
    cr_expect(eq(int, fib(5), 5));         //Should always pass; fifth Fibonacci Sequence 5 = 5
}

/***********************************************************************************************************
 In this Criterion test, we are testing if the fifth Fibonacci Sequence 5 equals 6. Since this is always 
 false, this test should always fail.
 @param suite2 (string) - The name of your testing suite. May be any alphanumeric string.
 @param fibonacci2 (string) - The name of your test. May be any alphanumeric string.
************************************************************************************************************/
Test(suite2, fibonacci2) {
    cr_expect(eq(int, fib(5), 6));         //Should always fail; fifth Fibonacci Sequence 5 != 6 it equals 5
}

/***********************************************************************************************************
 In this Criterion test, we are testing if the fifth Fibonacci Sequence 5 equals 5. Since this is always 
 true, this test should always pass.
 @param suite2 (string) - The name of your testing suite. May be any alphanumeric string.
 @param fibonacci3 (string) - The name of your test. May be any alphanumeric string.
 @param .init (function) - [optional] Pass in the name of your setup function. Function must be defined.
************************************************************************************************************/
Test(suite2, fibonacci3, .init = setup1) {
    cr_expect(eq(int, fib(5), testValue));         //Should always pass; fifth Fibonacci Sequence 5 = 5
}

/***********************************************************************************************************
 In this Criterion test, we are testing if the fifth Fibonacci Sequence 5 equals 6. Since this is always 
 false, this test should always fail.
 @param suite2 (string) - The name of your testing suite. May be any alphanumeric string.
 @param fibonacci4 (string) - The name of your test. May be any alphanumeric string.
 @param .init (function) - [optional] Pass in the name of your setup function. Function must be defined.
************************************************************************************************************/
Test(suite2, fibonacci4, .init = setup3) {
    cr_expect(eq(int, fib(5), testValue));         //Should always fail; fifth Fibonacci Sequence 5 != 6 it equals 5
}

Michaels_Criterion_tests.h

#ifndef MICHALES_CRITERION_TEST_H
#define MICHALES_CRITERION_TEST_H

//Function declarations
void setup(void);
void teardown(void);
void setup2(void);
void setup3(void);
void setup4(void);
void setup5(void);
void setup6(void);
void setup7(void);

#endif /* MICHALES_CRITERION_TEST_H */

lordmichael95 · 2024-03-17T21:41:41Z

lordmichael95
Mar 17, 2024
Author

Bumping the discussion so that someone might see it and reply.

0 replies

Snaipe · 2024-03-18T15:36:38Z

Snaipe
Mar 18, 2024
Maintainer

Can you try to minimize your example down to something that happens to break? It definitely works for me if I compile the sample main.

$ cat main.c
#include <stdio.h>
#include <criterion/criterion.h>

/* This is necessary on windows, as BoxFort needs the main to be exported
   in order to find it. */
#if defined (_WIN32) || defined (__CYGWIN__)
# if defined (_MSC_VER)
#  define DLLEXPORT __declspec(dllexport)
# elif defined (__GNUC__)
#  define DLLEXPORT __attribute__((dllexport))
# else
#  error No dllexport attribute
# endif
#else
# define DLLEXPORT
#endif

DLLEXPORT int main(int argc, char *argv[]) {
	printf("Hello, World!\n");

	struct criterion_test_set *tests = criterion_initialize();

	int result = 0;
	if (criterion_handle_args(argc, argv, true))
		result = !criterion_run_all_tests(tests);

	criterion_finalize(tests);
	return result;
}

$ gcc -o test ./main.c -lcriterion
$ ./test
Hello, World!
[====] Synthesis: Tested: 0 | Passing: 0 | Failing: 0 | Crashing: 0

2 replies

Snaipe Mar 18, 2024
Maintainer

Also, can you share some details about the platform you're using? Linux/macOS/Windows/something else?

lordmichael95 Mar 20, 2024
Author

Also, can you share some details about the platform you're using? Linux/macOS/Windows/something else?

Absolutely! I have an Ubuntu machine. Here is the output from uname -a:

Linux mlayman-ThinkStation-P3-Tower 6.2.0-26-generic #26~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Thu Jul 13 16:27:29 UTC 2 x86_64 x86_64 x86_64 GNU/Linux

Is there any other system information you would like to know?

lordmichael95 · 2024-03-20T04:11:43Z

lordmichael95
Mar 20, 2024
Author

Can you try to minimize your example down to something that happens to break? It definitely works for me if I compile the sample main.

$ cat main.c
#include <stdio.h>
#include <criterion/criterion.h>

/* This is necessary on windows, as BoxFort needs the main to be exported
   in order to find it. */
#if defined (_WIN32) || defined (__CYGWIN__)
# if defined (_MSC_VER)
#  define DLLEXPORT __declspec(dllexport)
# elif defined (__GNUC__)
#  define DLLEXPORT __attribute__((dllexport))
# else
#  error No dllexport attribute
# endif
#else
# define DLLEXPORT
#endif

DLLEXPORT int main(int argc, char *argv[]) {
	printf("Hello, World!\n");

	struct criterion_test_set *tests = criterion_initialize();

	int result = 0;
	if (criterion_handle_args(argc, argv, true))
		result = !criterion_run_all_tests(tests);

	criterion_finalize(tests);
	return result;
}

$ gcc -o test ./main.c -lcriterion
$ ./test
Hello, World!
[====] Synthesis: Tested: 0 | Passing: 0 | Failing: 0 | Crashing: 0

Sure! Here is a much smaller code base that consistently breaks:

main.c

#include <stdio.h>
#include <stdlib.h>
#include <criterion/criterion.h>


int main(int argc, char *argv[]) {
	printf("Hello, World! :)\n");

	struct criterion_test_set *tests = criterion_initialize();

	int result = 0;
	if (criterion_handle_args(argc, argv, true))
		result = !criterion_run_all_tests(tests);

	criterion_finalize(tests);
	return result;
}

Michaels_Criterion_tests.c

#include <stdio.h>
#include <stdlib.h>
#include <signal.h>
#include <criterion/criterion.h>
#include <criterion/new/assert.h>
#include "Michaels_Criterion_tests.h"




/***********************************************************************************************************
 In this Criterion test, we are testing if 5 equals 5. Since this is always true, this test should always
 pass.
 @param suite1 (string) - The name of your testing suite. May be any alphanumeric string.
 @param test1 (string) - The name of your test. May be any alphanumeric string.
************************************************************************************************************/
Test(suite1, test1) {
    cr_expect(eq(int, 5, 5));         //Should always pass; 5 = 5
}

makefile

#To build the test files:
#make BUILD_TYPE=test
#To build the production files:
#make
#To generate Doxygen documentation:
#make doc
#To get rid of all object and production executable files:
#make clean


#Compiler command - gcc for C; g++ for C++
CC = gcc
#Compiler flags
CFLAGS = -Wall -Wextra -g
#Location of the Criterion library
LDFLAGS = -L~/Documents/code/Criterion/include
#Name/Linking to the Criterion library
LDLIBS = -lcriterion

#Doxygen configuration filename. Defualt name is: Doxyfile
DOX_CONFIG = Doxyfile

#Source files
#PRODUCTION_SRCS = main.c fibonacci.c
PRODUCTION_SRCS = main.c  Michaels_Criterion_tests.c #fibonacci.c		###If Michaels_Criterion_tests.c is not compiled along with main.c, Criterion will be fine
TEST_SRCS = Michaels_Criterion_tests.c fibonacci.c
#TEST_SRCS = main.c

#If BUILD_TYPE = "test", use test files; else, use production files
ifeq ($(BUILD_TYPE), test)
    SRCS = $(TEST_SRCS)
    TARGET = testProgram
else
    SRCS = $(PRODUCTION_SRCS)
    TARGET = productionProgram
endif

#Object files
OBJS = $(SRCS:.c=.o)

#Specifies that "all", "clean", and "doc" are not actual files or folders
.PHONY: all clean doc

all: $(TARGET)

$(TARGET): $(OBJS)
	$(CC) $(CFLAGS) $(LDFLAGS) -o $@ $^ $(LDLIBS)

%.o: %.c
	$(CC) $(CFLAGS) -c -o $@ $<

clean:
	$(RM) $(OBJS) $(TARGET)

#Doxygen documentation generation
doc:
	doxygen $(DOX_CONFIG)

Terminal Output:

mlayman@mlayman-ThinkStation-P3-Tower:~/Documents/code/other-project$ make
gcc -Wall -Wextra -g -c -o main.o main.c
gcc -Wall -Wextra -g -L~/Documents/code/Criterion/include -o productionProgram main.o Michaels_Criterion_tests.o -lcriterion
mlayman@mlayman-ThinkStation-P3-Tower:~/Documents/code/other-project$ ./productionProgram 
Hello, World! :)
Hello, World! :)
criterion: Re-entering criterion from a test worker. This is a catastrophic bug, please report it on the issue tracker.
Bailing out to avoid fork-bombing the system.
criterion: Could not spawn test instance: Protocol error
Aborted (core dumped)

Oddly, I see "Hello, World! :)" printed twice to the terminal.

1 reply

Snaipe Mar 25, 2024
Maintainer

Can you try to disable LTO? Weirdly enough the only thing I can think of is that the initializer in the .init section did not run for some reason

lordmichael95 · 2024-03-29T04:22:29Z

lordmichael95
Mar 29, 2024
Author

Can you try to disable LTO? Weirdly enough the only thing I can think of is that the initializer in the .init section did not run for some reason

Assuming by LTO you mean Link Time Optimization, disabling LTO does not seem to have an effect. I used this link and export DEB_BUILD_MAINT_OPTIONS=optimize=-lto to disable LTO in theory. However, I am not confident that I actually disabled LTO. The article mentions a "rules file" to enable/disable LTO. But I am not sure where that might be located. Looking in /usr/lib/udev/rules.d I did not see an obvious rules file for LTO.

Terminal Output:

export DEB_BUILD_MAINT_OPTIONS=optimize=-lto
mlayman@mlayman-ThinkStation-P3-Tower:~/Documents/code/other-project$ make clean
rm -f main.o Michaels_Criterion_tests.o productionProgram
mlayman@mlayman-ThinkStation-P3-Tower:~/Documents/code/other-project$ make
gcc -Wall -Wextra -g -c -o main.o main.c
gcc -Wall -Wextra -g -c -o Michaels_Criterion_tests.o Michaels_Criterion_tests.c
gcc -Wall -Wextra -g -L~/Documents/code/Criterion/include -o productionProgram main.o Michaels_Criterion_tests.o -lcriterion
mlayman@mlayman-ThinkStation-P3-Tower:~/Documents/code/other-project$ ./productionProgram 
Hello, World! :)
Hello, World! :)
criterion: Re-entering criterion from a test worker. This is a catastrophic bug, please report it on the issue tracker.
Bailing out to avoid fork-bombing the system.
criterion: Could not spawn test instance: Protocol error
Aborted (core dumped)

Did I go about disabling LTO correctly? If not, how should I disable LTO?

3 replies

Snaipe Mar 29, 2024
Maintainer

No, that's an environment variable that changes the behavior of the debian build system, but you're compiling criterion manually.

I believe for gcc it's something like -fno-lto.

Snaipe Mar 29, 2024
Maintainer

Also try -fno-pie since that may cause boxfort to not being able to find the main function.

lordmichael95 Apr 9, 2024
Author

I apologize for the delay in getting back to you.

No, that's an environment variable that changes the behavior of the debian build system, but you're compiling criterion manually.

I believe for gcc it's something like -fno-lto.

Also try -fno-pie since that may cause boxfort to not being able to find the main function.

I tried several variations involving the flags without success. :( -fno-pie appears to be an incorrect flag as this error is thrown:

/usr/bin/ld: main.o: relocation R_X86_64_32 against `.rodata' can not be used when making a PIE object; recompile with -fPIE
/usr/bin/ld: failed to set dynamic section sizes: bad value
collect2: error: ld returned 1 exit status

As it recommends, I recompile with -fPIE. However that still results in a core dump when running the executable.

Terminal Output

mlayman@mlayman-ThinkStation-P3-Tower:~/Documents/code/other-project$ make clean
rm -f main.o Michaels_Criterion_tests.o productionProgram
mlayman@mlayman-ThinkStation-P3-Tower:~/Documents/code/other-project$ 
mlayman@mlayman-ThinkStation-P3-Tower:~/Documents/code/other-project$ 
mlayman@mlayman-ThinkStation-P3-Tower:~/Documents/code/other-project$ make
gcc -Wall -Wextra -g -fno-lto -fno-pie		 -c -o main.o main.c
gcc -Wall -Wextra -g -fno-lto -fno-pie		 -c -o Michaels_Criterion_tests.o Michaels_Criterion_tests.c
gcc -Wall -Wextra -g -fno-lto -fno-pie		 -L~/Documents/code/Criterion/include -o productionProgram main.o Michaels_Criterion_tests.o -lcriterion
/usr/bin/ld: main.o: relocation R_X86_64_32 against `.rodata' can not be used when making a PIE object; recompile with -fPIE
/usr/bin/ld: failed to set dynamic section sizes: bad value
collect2: error: ld returned 1 exit status
make: *** [makefile:47: productionProgram] Error 1
mlayman@mlayman-ThinkStation-P3-Tower:~/Documents/code/other-project$ 
mlayman@mlayman-ThinkStation-P3-Tower:~/Documents/code/other-project$ 
mlayman@mlayman-ThinkStation-P3-Tower:~/Documents/code/other-project$ make clean
rm -f main.o Michaels_Criterion_tests.o productionProgram
mlayman@mlayman-ThinkStation-P3-Tower:~/Documents/code/other-project$ 
mlayman@mlayman-ThinkStation-P3-Tower:~/Documents/code/other-project$ 
mlayman@mlayman-ThinkStation-P3-Tower:~/Documents/code/other-project$ 
mlayman@mlayman-ThinkStation-P3-Tower:~/Documents/code/other-project$ make
gcc -Wall -Wextra -g -fno-lto -fPIE		 -c -o main.o main.c
gcc -Wall -Wextra -g -fno-lto -fPIE		 -c -o Michaels_Criterion_tests.o Michaels_Criterion_tests.c
gcc -Wall -Wextra -g -fno-lto -fPIE		 -L~/Documents/code/Criterion/include -o productionProgram main.o Michaels_Criterion_tests.o -lcriterion
mlayman@mlayman-ThinkStation-P3-Tower:~/Documents/code/other-project$ ./productionProgram 
Hello, World! :)
Hello, World! :)
criterion: Re-entering criterion from a test worker. This is a catastrophic bug, please report it on the issue tracker.
Bailing out to avoid fork-bombing the system.
criterion: Could not spawn test instance: Protocol error
Aborted (core dumped)
mlayman@mlayman-ThinkStation-P3-Tower:~/Documents/code/other-project$ make clean
rm -f main.o Michaels_Criterion_tests.o productionProgram
mlayman@mlayman-ThinkStation-P3-Tower:~/Documents/code/other-project$ 
mlayman@mlayman-ThinkStation-P3-Tower:~/Documents/code/other-project$ 
mlayman@mlayman-ThinkStation-P3-Tower:~/Documents/code/other-project$ make
gcc -Wall -Wextra -g -fPIE		 -c -o main.o main.c
gcc -Wall -Wextra -g -fPIE		 -c -o Michaels_Criterion_tests.o Michaels_Criterion_tests.c
gcc -Wall -Wextra -g -fPIE		 -L~/Documents/code/Criterion/include -o productionProgram main.o Michaels_Criterion_tests.o -lcriterion
mlayman@mlayman-ThinkStation-P3-Tower:~/Documents/code/other-project$ ./productionProgram 
Hello, World! :)
Hello, World! :)
criterion: Re-entering criterion from a test worker. This is a catastrophic bug, please report it on the issue tracker.
Bailing out to avoid fork-bombing the system.
criterion: Could not spawn test instance: Protocol error
Aborted (core dumped)
mlayman@mlayman-ThinkStation-P3-Tower:~/Documents/code/other-project$ make clean
rm -f main.o Michaels_Criterion_tests.o productionProgram
mlayman@mlayman-ThinkStation-P3-Tower:~/Documents/code/other-project$ 
mlayman@mlayman-ThinkStation-P3-Tower:~/Documents/code/other-project$ 
mlayman@mlayman-ThinkStation-P3-Tower:~/Documents/code/other-project$ make
gcc -Wall -Wextra -g -fno-lto		 -c -o main.o main.c
gcc -Wall -Wextra -g -fno-lto		 -c -o Michaels_Criterion_tests.o Michaels_Criterion_tests.c
gcc -Wall -Wextra -g -fno-lto		 -L~/Documents/code/Criterion/include -o productionProgram main.o Michaels_Criterion_tests.o -lcriterion
mlayman@mlayman-ThinkStation-P3-Tower:~/Documents/code/other-project$ ./productionProgram 
Hello, World! :)
Hello, World! :)
criterion: Re-entering criterion from a test worker. This is a catastrophic bug, please report it on the issue tracker.
Bailing out to avoid fork-bombing the system.
criterion: Could not spawn test instance: Protocol error
Aborted (core dumped)
mlayman@mlayman-ThinkStation-P3-Tower:~/Documents/code/other-project$

Not really sure what next steps should be. Would you like me to adjust whatever the settings are to get core files to actually generate (assuming the core files would be useful to you)?

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Trying to Use Criterion with My Main Function #526

{{title}}

{{editor}}'s edit

{{editor}}'s edit

Replies: 4 comments 6 replies

{{title}}

{{title}}

{{title}}

{{title}}

{{editor}}'s edit

{{editor}}'s edit

{{title}}

{{editor}}'s edit

{{editor}}'s edit

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{editor}}'s edit

{{editor}}'s edit

Select a reply

Trying to Use Criterion with My Main Function #526

lordmichael95 Mar 13, 2024

Replies: 4 comments · 6 replies

lordmichael95 Mar 17, 2024 Author

Snaipe Mar 18, 2024 Maintainer

Snaipe Mar 18, 2024 Maintainer

lordmichael95 Mar 20, 2024 Author

lordmichael95 Mar 20, 2024 Author

Snaipe Mar 25, 2024 Maintainer

lordmichael95 Mar 29, 2024 Author

Snaipe Mar 29, 2024 Maintainer

Snaipe Mar 29, 2024 Maintainer

lordmichael95 Apr 9, 2024 Author

lordmichael95
Mar 13, 2024

Replies: 4 comments 6 replies

lordmichael95
Mar 17, 2024
Author

Snaipe
Mar 18, 2024
Maintainer

Snaipe Mar 18, 2024
Maintainer

lordmichael95 Mar 20, 2024
Author

lordmichael95
Mar 20, 2024
Author

Snaipe Mar 25, 2024
Maintainer

lordmichael95
Mar 29, 2024
Author

Snaipe Mar 29, 2024
Maintainer

Snaipe Mar 29, 2024
Maintainer

lordmichael95 Apr 9, 2024
Author