After I have succesfully turned some of my colleagues from Prolog
hackers ):-( into Haskell lovers :-) , I'm now in a quite embarrasing
situation: Debugging features/environments are virtually nonexistant! So
we had to resort to inserting trace expressions (or should I say
"instructions"?) throughout the suspected code (aka printf debugging to
C programmers). This is definitely not the way one would like to debug
at the end of the 90s. Consequently, after the initial euphoria there is
a feeling of frustration around here. So here is my question:
How do people out there debug Haskell programs???
Please note that I am not talking about toy programs of a few dozen
lines. How do e.g. the people at Glasgow find the bugs in GHC (which is
a fairly large Haskell program)?
The question can easily be generalised from "Haskell" to "any lazy
function language". So, if there are good tips for e.g. Miranda, I
wouldn't mind! ;-)
I'm aware that this is a kind of "What's the meaning of life?" question,
but any help/hints would be appreciated. By the way, are there any
newsgroups or mailing lists out there which are more specific to this
kind of problem?
[Help is desperately needed. Otherwise the Prolog menace is waiting for
me again... :-( ]
--
Sven Panne Tel.: +49/89/2178-2235
LMU, Institut fuer Informatik FAX : +49/89/2178-2211
LFE Programmier- und Modellierungssprachen Oettingenstr. 67
mailto:[EMAIL PROTECTED] D-80538 Muenchen
http://www.pms.informatik.uni-muenchen.de/mitarbeiter/panne
