Skip to content

Improve parser error reporting in `ghc-pkg`

Here's what I was confronted recently due to a broken sandbox environment:

$ cabal info parsec
cabal: ghc-pkg: Data.Binary.Get.runGet at position 9583: demandInput: not enough bytes

The main problem is that this message is not very helpful (other than telling that ghc-pkg wasn't able to do something). Duncan told me, that the recent binary API now provides better facilities for error reporting. That could be used to improve the UI of ghc-pkg when reporting errors.

Trac metadata
Trac field Value
Version 7.8.2
Type Task
TypeOfFailure OtherFailure
Priority normal
Resolution Unresolved
Component ghc-pkg
Test case
Differential revisions
BlockedBy
Related
Blocking
CC duncan
Operating system
Architecture
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information