Yeh, that was why "for some reason" — in that case I'd blame the audit framework, not the program.

ghc_ticker is an internal thread of the ghc runtime, so you want the ghc Trac, rts component. https://ghc.haskell.org/trac/ghc/newticket?type=bug (you will need to create an account).

On Mon, Jun 18, 2018 at 4:48 AM Jon Fairbairn <jon.fairbairn@cl.cam.ac.uk> wrote:
Brandon Allbery <allbery.b@gmail.com> writes:

> I'd suspect it's mishandling the error return from a read(). Or not
> handling, but if the error it gets back is for some reason EAGAIN then it's
> kinda difficult to handle this sanely except by adding extra
> instrumentation to catch the loop.

If a selinux denial is producing EAGAIN, something is very
wrong. I doubt that that’s what’s happening. If I knew where to
go I could create a ticket…


_______________________________________________
Haskell-Cafe mailing list
To (un)subscribe, modify options or view archives go to:
http://mail.haskell.org/cgi-bin/mailman/listinfo/haskell-cafe
Only members subscribed via the mailman list are allowed to post.


--
brandon s allbery kf8nh                               sine nomine associates
allbery.b@gmail.com                                  ballbery@sinenomine.net
unix, openafs, kerberos, infrastructure, xmonad        http://sinenomine.net