On Thu, Jan 06, 2000 at 11:10:54 +0100, Sven Panne wrote:
> This lead to hours of fun...
Same with me, and after (repeat reduce) led me to the presented
example program, I poked around in the generated .hc and .s files (which is
really, really no fun), trying to narrow the fault case even more. Well,
this wasn't really successful, I merely found that the
`PrelPack_unpackCStringIO.*' closure is called before AND after `free' frees
the strdup'd memory...
Now, I'm a little bit curious about how The GHC Team members track such
errors... For example, it was quite annoying that every compiler run changes
those c1XY_{info,ret,...} symbol names (yes, I already used '-S' and
'-keep-hc-files-too' to have at least a sync'ed set of .hc,.s,.o files).
Is there a description of the low-level details of the RTS out there, or
other help that makes debugging easier?
> Nice to see that I'm not insane after all! %-)
Seems to be just another of the "I'm slightly going mad..." cases... ;-)
Cheers,
Michael
--
Lehrstuhl-Gärtnerei Michael Weber <[EMAIL PROTECTED]>
Lehrstuhl für Informatik II
RWTH Aachen
WWW: http://www-i2.informatik.rwth-aachen.de/Software/Haskell/
