#5748: ghci segfault on OS X after dlsym failed lookup
---------------------------------+------------------------------------------
    Reporter:  gwright           |       Owner:  gwright   
        Type:  bug               |      Status:  patch     
    Priority:  normal            |   Milestone:            
   Component:  GHCi              |     Version:  7.2.1     
    Keywords:                    |          Os:  MacOS X   
Architecture:  Unknown/Multiple  |     Failure:  GHCi crash
  Difficulty:  Unknown           |    Testcase:            
   Blockedby:                    |    Blocking:            
     Related:                    |  
---------------------------------+------------------------------------------

Comment(by gwright):

 Replying to [comment:9 simonmar]:
 > Thanks, I'll look at your patch.
 >
 > It's hard to know whether `.hs-boot` files are causing your missing
 symbol, but if all you're doing is compiling a library and loading it into
 GHCi, a missing symbol definitely indicates a bug in GHC.  Can you reduce
 the example as much as possible and attach it?

 It seems that the original bug is not a bug, but an infelicity in cabal.
 The library is built using cabal.  Cabal compiles all of the modules, but
 if a module is left off the {{{Other-modules}}} list, it isn't linked.
 This causes the unresolved symbol.  I had been refactoring the modules in
 my library and hadn't noticed that one was left off the {{{Other-
 modules}}} list.

 It's annoying that cabal doesn't produce a warning when it fails to link a
 module that has been compiled.  However, the only real bug here --- the
 linker segfault --- is fixed by the patch.  When the patch is applied this
 ticket can be closed.

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

_______________________________________________
Glasgow-haskell-bugs mailing list
Glasgow-haskell-bugs@haskell.org
http://www.haskell.org/mailman/listinfo/glasgow-haskell-bugs

Reply via email to