Radar:26456448 Camden
> On May 24, 2016, at 1:10 PM, Kevin Elliott <kelli...@mac.com> wrote: > > >> On May 24, 2016, at 11:50 AM, Quinn The Eskimo! <eski...@apple.com> wrote: >> >> >> On 24 May 2016, at 18:52, Camden Narzt <camden.na...@hotmail.com> wrote: >> >>> Does anyone have any ideas about why this is happening? >> >> The answer to the question “Why does my system kernel panic?” is pretty much >> always “Because of a bug in the OS?” The system is not supposed to panic >> unless you do obviously dodgy things (like load KEXTs). > > One quick note on this- what Quinn is saying here is 100% correct, but not > necessarily good for you. The fact that the kernel shouldn’t panic does NOT > mean that your code should work. While it’s possible that this is entirely > an OS level issue, what’s often the case is that OS X is failing to catch > something dodgy and that failure eventually leads to a panic. Fixing the > issue is OS X means catching the problem earlier and doing something “nice” > like crashing/hanging the triggering process, not making the dodgy thing > work. > > I have no idea what homebrew.mxcl.opentsdb.plist is kicking off, but it’s > very likely that getting this to work is going to involved changes to > homebrew and/or opentsdb, even after the kernel panic is fixed. > > -Kevin > _______________________________________________ > launchd-dev mailing list > launchd-dev@lists.macosforge.org > https://lists.macosforge.org/mailman/listinfo/launchd-dev _______________________________________________ launchd-dev mailing list launchd-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/launchd-dev
