Ouch, with all the great Haskell parsers like Parsec around I think I was expecting a line/column number :-)

But I see a ticket is already open for this
http://trac.haskell.org/haddock/ticket/83

On Wed, Aug 26, 2009 at 2:47 AM, Gwern Branwen <gwern0@gmail.com> wrote:
On Tue, Aug 25, 2009 at 8:30 PM, Peter Verswyvelen<bugfact@gmail.com> wrote:
> I'm getting the error mentioned in the subject, but without any indication
> where in my file this error occurs.
> What does this mean?
> Thanks,
> Peter

It means exactly that - something in that file's comments is causing
Haddock to choke. It could be using '*' inside some --s, it could be
something else. Haddock won't really say. Your best bet is the old
bisect/binary-search method: remove half the comments & retry,
narrowing it down until you've found the offending line and then
character. Then you can either remove it or read the Haddock manual
and see what the right thing looks like.

--
gwern