bash-engine: Don't use RLIMIT_NOFILE on FreeBSD (broken), dump json i…

…n github actions

.github/workflows/freebsd-build.sh

@@ -14,6 +14,10 @@ run () {
   cmake -DCMAKE_INSTALL_PREFIX=/usr/local ../tests || exit 64
   make || exit 64
   cd ..
+
+  chmod u+x .github/workflows/test-executable.sh
+  kcov --include-pattern=test-executable.sh coverage .github/workflows/test-executable.sh
+  cat coverage/test-executable.sh/coverage.json
 }
 
 run "$@"

src/configuration.cc

@@ -5,6 +5,7 @@
 #include <getopt.h>
 #include <limits.h>
 #include <sys/stat.h>
+#include <sys/param.h>
 #include <sys/types.h>
 #include <unistd.h>
 #include <map>

src/engines/bash-engine.cc

@@ -153,6 +153,8 @@ class BashEngine : public ScriptEngineBase
 			unsigned int argc = conf.getArgc();
 			int xtraceFd = 782; // Typical bash users use 3,4 etc but not high fd numbers (?)
 			{
+// This doesn't work on (recent?) FreeBSDs, so disable for now
+#ifndef __FreeBSD__
 				// However, the range of fd numbers that this process can use is limited by the caller of this process.
 				// The following code specification will require discussion with many kcov users.
 				struct rlimit rlim;
@@ -161,6 +163,7 @@ class BashEngine : public ScriptEngineBase
 					return false;
 				}
 				xtraceFd = rlim.rlim_cur / 4;
+#endif
 			}
 			const std::string command = conf.keyAsString("bash-command");
 			bool usePS4 = conf.keyAsInt("bash-use-ps4");