+sub valdebugunattended
+{
+ # NOTE: To make sure valgrind generates coredumps, set soft core limit in /etc/security/limits.conf to unlimited
+ # Check to see its not 'running' already.
+ if (getstatus() == 1) { print "InspIRCd is already running.\n"; return 0; }
+
+ print "$binpath/$executable doesn't exist\n" and return 0 unless(-e "$binpath/$executable");
+ print "$binpath/$executable is not executable\n" and return 0 unless(-f "$binpath/$executable" && -x "$binpath/$executable");
+
+ # Check we have valgrind and gdb
+ checkvalgrind();
+ checkgdb();
+
+ # If we are still alive here.. Try starting the IRCd..
+ # May want to do something with these args at some point: --suppressions=.inspircd.sup --gen-suppressions=yes
+ # Could be useful when we want to stop it complaining about things we're sure aren't issues.
+ #
+ # NOTE: Saving the debug log (redirected stdout), while useful, is a potential security risk AND one hell of a spacehog. DO NOT SAVE THIS WHERE EVERYONE HAS ACCESS!
+ # Redirect stdout to /dev/null if you're worried about the security.
+ #
+ my $pid = fork;
+ if ($pid == 0) {
+ POSIX::setsid();
+ umask 022;
+ open STDERR, '>', "$valgrindlogpath/valdebug.$$" or die $!;
+ umask 066;
+ open STDIN, '/dev/null' or die $!;
+ open STDOUT, '>', "$valgrindlogpath/out.$$" or die $!;
+ exec "valgrind -v --tool=memcheck --leak-check=yes --num-callers=10 --time-stamp=yes --log-fd=2 $binpath/$executable -nofork -debug -nolog";
+ exit 1;
+ }
+}
+