https://bugzilla.redhat.com/show_bug.cgi?id=1324922
John Eckersberg <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?([email protected] | |om) | --- Comment #8 from John Eckersberg <[email protected]> --- OK, let's regroup and clarify some things here before we get more confused. Part of this is my fault because I directed you on IRC to post on the bodhi update about your crash. I didn't realize at first that you were seeing an IPv6 crash and thought it was just the logging crash. Anyway... This particular bug is about broken logging. The current released version (R16B-03.16.el7) has broken logging. The only change[1] in the .17 release is to revert the patch that added the broken logging. So I would ask two things. (1) Ignore the IPv6 thing for this bug. It would be a huge help if you could just sanity check that .16 has broken logging and that .17 is correct (and update karma on the update accordingly). Then we can either ship that update ASAP or bundle it with an IPv6 fix (if we can get it quickly). (2) We'll file another bug for the IPv6 issue. We already fixed one crash bug in https://bugzilla.redhat.com/show_bug.cgi?id=1310808 (incidentally this is the update you said introduced your crash). If you can get it to reproduce and capture a coredump of the crash that would be awesome. I will try to reproduce as well by toying with ERL_EPMD_ADDRESS on my end. [1] http://pkgs.fedoraproject.org/cgit/rpms/erlang.git/commit/?h=epel7&id=6515854c294bc6be60987407a54d9680fd8faf65 -- You are receiving this mail because: You are on the CC list for the bug. _______________________________________________ erlang mailing list [email protected] http://lists.fedoraproject.org/admin/lists/[email protected]
