[systemd-devel] Soliciting feedback for golang bindings to the systemd journal C API

[Brandon Philips]

On Thu, Jun 19, 2014 at 12:37 PM, Dan Mace <dmace at redhat.com> wrote:
> This is on my backburner at the moment while I work on some other things.  Hitting the segfault while testing our primary use case and being unable to reproduce the error made me nervous enough that I don't feel comfortable promoting any of the current work yet.  I was hoping something obvious would jump out, or somebody else running the test from my branch would be able to observe the segfault and have a better ability to debug.  My branch[1] is still in the same state as before.  I don't think a PR makes sense quite yet until there's increased confidence in the stability.  Without knowing the cause, I can't predict the impact to the design that might come with the solution.

Maybe it is some random bug with Go 1.2? Go 1.3 is out now.