LGMP | A shared memory message based broadcast system | Application Framework library

The problem occurred when ruby was installed using sudo apt install ruby.

Solution: Install ruby via RVM.

Here are some issues that might be causing your segmentation fault:

1. Both the buffer c and c2 are declared on the stack, and not null-terminated. You're unsafely assuming they are null-terminated. This can easily be a source of a segfault when you try to printf these buffers (printf always searches for the null character as an indication of the end of the buffer)
2. You are using strcat in the same way on a non-nulled buffer that you allocate for your 2D boards (strcat(boards[count][sub_board_count], c);). You malloc'd these buffers but that memory isn't guaranteed to be zero. strcat also looks for a null character to indicate where to begin concatenating.
3. You indefinitely read in boards from the file boards_file, and never check to see if you have capacity. You've fixed your board count at 730 (#define BOARDS 730). If the file contains more, you'll also get a segmentation fault because you don't perform a bounds check.

• Always zero your stack buffers. You can do this with: char c[N] = {0}; // Zeroes the entire buffer.
• Always zero your allocated memory, if you'll be storing strings in them and using C string functions. So either use memset or calloc to allocate them zeroed.

From looking at GDB's configure script, I think the problem is that GDB is not picking up the --with-gmp-include and --with-gmp-lib configure flags. These flags are handled in the toplevel configure script and made available to each sub-component (GDB, binutils, ld, etc) through the environment, and it looks like GDB doesn't pick these up.

The easiest way to move forward will be to override CFLAGS and CXXFLAGS at configure time, like:

I ended up with the following CMake File which gets the job done. Note that I am now building a Shared library. Furthermore, I actually did not specify any compiler flags. In the end it was just a matter of linking the correct libraries.

The -Wall flag in the AM_INIT_AUTOMAKE(...) invocation refers to warnings from automake and related tools like aclocal, not to compiler warnings. You will see these warnings when you are running autoreconf.

Note that while you can also add -Werror to AM_INIT_AUTOMAKE(...) to make your autoreconf run fail on warnings, many common macros (like those shipped with gettext or libtool) will still use deprecated macros which generates a warning, so -Werror means you cannot use this standard set of tools, so -Werror is not very useful in many cases.

If you want to add compiler options, there are a third party macros (e.g. AX_CHECK_COMPILE_FLAG) which test whether the compiler recognizes a given compile option and you can then add them to some variable and use that in places. That is a different stackoverflow question, though.

I don't know anything about GMP, but you seem to include the wrong header.

#include worked for me.

General polygons with possibly circular edges don't have the area function - so we need to get into details of their representation and write this kind of functions ourselves (sigh!!). An example of such an area function is below:

Use an older version of boost from that time period