Validating the HEAD today on Mac OS X gives me

Unexpected failures:
   ghci024(ghci)

This is probably related to the new debugger-related patches from yesterday. It'd be good to keep validate *break free* (or is this an OS issue)?

ghci now has the ability to show dynamic flag settings
and language flags, and that is the test for it. as far as
i know, we've accounted for all platform issues, but as
there wasn't any other test of all flags before, only this one will show up in validate runs after flag changes.

since adding that feature, there have been several Changes to compiler/main/DynFlags.hs:

   Tue Nov 13 17:45:39 GMT Standard Time 2007  Pepe Iborra <[EMAIL PROTECTED]>
     * GHCi debugger: added a new flag, -fno-print-binding-contents
The contents of bindings show at breakpoints and by :show bindings
     is rendered using the same printer that :print uses.
     But sometimes the output it gives spans over too many lines and the
     user may want to be able to disable it.
Thu Oct 4 21:47:18 GMT Daylight Time 2007 Pepe Iborra <[EMAIL PROTECTED]>
     *  Leftovers from the 1st GHCi debugger prototype
Tue Nov 13 15:32:57 GMT Standard Time 2007 Simon Marlow <[EMAIL PROTECTED]>
     * FIX #1653 (partially): add -X flags to completion for :set
Sun Nov 11 00:11:26 GMT Standard Time 2007 Ian Lynagh <[EMAIL PROTECTED]>
     * Turn -fprint-bind-result off by default
Wed Nov 7 10:26:48 GMT Standard Time 2007 Simon Marlow <[EMAIL PROTECTED]>
     * #1617: Add :browse! and various other additions to GHCi

the change to -fprint-bind-result was covered, but hasn't
been propagated everywhere yet. in addition to that, linux head buildbot sees:

-  -fno-ignore-breakpoints
+  -fprint-bind-contents

confirming your debugger suggestion, although the flag
name looks shortened. Pepe?-)

the changes for ghci024 would need to be made in

   testsuite/tests/ghc-regress/ghci/scripts/ghci024.py

which generates the platform- and version-spefic
ghci024.stdout for this test.

btw, i've never seen a clean validate run on my system (win/xp), as ThreadDelay001(normal) fails consistently.

claus

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

Reply via email to