[GHC] #13529: eventlog to report more information about stopping threads because of FFI calls

GHC ghc-devs at haskell.org
Wed Apr 5 14:45:09 UTC 2017


#13529: eventlog to report more information about stopping threads because of FFI
calls
-------------------------------------+-------------------------------------
        Reporter:  varosi            |                Owner:  (none)
            Type:  feature request   |               Status:  new
        Priority:  normal            |            Milestone:
       Component:  Profiling         |              Version:  8.0.2
      Resolution:                    |             Keywords:
Operating System:  Unknown/Multiple  |         Architecture:  x86_64
                                     |  (amd64)
 Type of failure:  None/Unknown      |            Test Case:
      Blocked By:                    |             Blocking:
 Related Tickets:                    |  Differential Rev(s):
       Wiki Page:                    |
-------------------------------------+-------------------------------------

Comment (by bgamari):

 How do you propose we would identify which foreign function is being
 called? I can think of a few ways,

  * Have the compiler produce a string which is passed to the RTS when
 generating code for safe foreign calls
  * Use the symbol table lookup of the callee's address
  * Use DWARF information of the callee's address

 All of these have their costs and I do wonder whether this sort of
 instrumentation might not be better left to the user to implement
 themselves with, e.g. `traceEvent`, if they need it.

--
Ticket URL: <http://ghc.haskell.org/trac/ghc/ticket/13529#comment:1>
GHC <http://www.haskell.org/ghc/>
The Glasgow Haskell Compiler


More information about the ghc-tickets mailing list