Date: Thu, 27 Apr 2017 13:48:45 +0100 From: Edward Napierala <trasz@freebsd.org> To: Willem Jan Withagen <wjw@digiware.nl> Cc: "freebsd-hackers@freebsd.org" <freebsd-hackers@freebsd.org> Subject: Re: Disabling program core dumps Message-ID: <CAFLM3-pjR_wDVnjuUhZmtnaWvAX4SGvVbYhYAp-02148oUtv8A@mail.gmail.com> In-Reply-To: <32ac85ed-f0e5-2f80-299a-3bb1166cd5e6@digiware.nl> References: <32ac85ed-f0e5-2f80-299a-3bb1166cd5e6@digiware.nl>
next in thread | previous in thread | raw e-mail | index | archive | help
There's the kern.coredump sysctl, which makes it possible to disable coredumping globally. 2017-04-27 13:36 GMT+01:00 Willem Jan Withagen <wjw@digiware.nl>: > Hi, > > Running (googletest) tests some are expected to die: EXPECT_DEATH(). > This normally dumps a core, but since it is expected that core is rather > useless. > > Thusfar I've found the best way to limit a program to dump core (from > within the program) is to set its RLIMIT_CORE to 0. > > So I can do this before the test, and then set the old size back once > the test is finished. > > Or is there another way, like setting a flag in process state (which I > have not been able to find) > > --WjW > _______________________________________________ > freebsd-hackers@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-hackers > To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org" >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAFLM3-pjR_wDVnjuUhZmtnaWvAX4SGvVbYhYAp-02148oUtv8A>