hi,

on winxp, using cygwin and the ghc head repo, i just tried to set a different boring file, and then accidentally typed

   darcs whatsnew -l --boring

instead of the intended

   darcs whatsnew -l

but, instead of giving lots of output quickly, darcs seemed
to hang, and indeed, gives an error message, though only
*after* interrupting with ctrl-c. not using --boring, or setting boringfile back to .darcs-boring, seems to cure the problem.

but when i interrupt darcs, strange things may happen as well, including the internal error i managed to capture below.

so, firstly, there seems to be something wrong with a scheduler in darcs, triggered by ignoring a non-standard boringfile, and, secondly, there is a ghc 6.6 bug sometimes triggered when interrupting realdarcs (perhaps the darcs binary for windows should be built with ghc 6.6.1 at least, or 6.8.1 soon?).

thirdly, while i'm at boringfiles: the ghc repo has nested
darcs repos below the main repo, of non-negligible size.
seeing the regex patterns in ghc's .darcs-boring, and the
time it takes to run its ./darcs-all script, makes me wonder:
if a directory matches a boring pattern, does darcs still
descend into it, or are such directories ignored completely?

claus

---- session log showing the two bugs
$ darcs --version
1.0.9 (release)

$ which darcs
/cygdrive/c/darcs/darcsdir-cygwin/darcs

$ darcs setpref boringfile dont-touch-these.boring
Changing value of boringfile from '.darcs-boring' to 'dont-touch-these.boring'

$ darcs whatsnew -l --boring
... <ctrl-c>
realdarcs.exe: schedule: re-entered unsafely.
  Perhaps a 'foreign import unsafe' should be 'safe'?

$ darcs setpref boringfile .darcs-boring
Changing value of boringfile from 'dont-touch-these.boring' to '.darcs-boring'

$ darcs whatsnew -l --boring
M ./compiler/basicTypes/RdrName.lhs -1 +6
M ./compiler/ghci/InteractiveUI.hs -46 +91
M ./compiler/main/GHC.hs +5
M ./compiler/parser/Parser.y.pp -1 +21
M ./docs/users_guide/ghci.xml -2 +9
realdarcs.exe: internal error: evacuate: strange closure type 9108
   (GHC version 6.6 for i386_unknown_mingw32)
   Please report this as a GHC bug:  http://www.haskell.org/ghc/reportabug

This application has requested the Runtime to terminate it in an unusual way.
Please contact the application's support team for more information.

_______________________________________________
Cvs-ghc mailing list
[email protected]
http://www.haskell.org/mailman/listinfo/cvs-ghc

Reply via email to