Date: Mon, 19 Dec 2016 12:27:30 -0800 From: Adrian Chadd <adrian.chadd@gmail.com> To: "freebsd-arch@freebsd.org" <freebsd-arch@freebsd.org> Cc: freebsd-current <freebsd-current@freebsd.org> Subject: Re: RFC: DTrace probes for debugging or testing in userland programs Message-ID: <CAJ-Vmon3%2BjMyfgBcVORyMoXX3JEAFCWtK2VPo9wWLN2hsS%2BrNA@mail.gmail.com> In-Reply-To: <20161220.043646.1181938468712455328.hrs@allbsd.org> References: <20161220.043646.1181938468712455328.hrs@allbsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi, I'd love to see a unified-ish logging API for FreeBSD applications. I always end up reusing some C code I have here that I based on some Squid style logging API in ages past. I could always polish it up and put it up for review. I'm not a big fan of requiring dtrace to use it though. On a lot of the embedded systems dtrace varies from "it's very big" through to "we don't have enough RAM/flash to do this". So although I like the sentiment, I don't think using dtrace for program logging is the right answer. I like what apple did to wrap the program logging stuff so people didn't just write their own libraries (hi!) and so there's a unified-ish way to interact with apple programs. I think we could do with that. Thanks, -adrian
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAJ-Vmon3%2BjMyfgBcVORyMoXX3JEAFCWtK2VPo9wWLN2hsS%2BrNA>