Opened 10 years ago

Closed 10 years ago

Last modified 7 years ago

#1155 closed bug (fixed)

ghci -debug generates slightly odd message

Reported by: Stefan O'Rear <stefanor@…> Owned by:
Priority: lowest Milestone: 6.8.1
Component: GHCi Version: 6.6
Keywords: Cc:
Operating System: Unknown/Multiple Architecture: Unknown/Multiple
Type of failure: None/Unknown Test Case:
Blocked By: Blocking:
Related Tickets: Differential Rev(s):
Wiki Page:


stefan@stefans:~$ ghci -debug fibbench/Y.hs
   ___         ___ _
  / _ \ /\  /\/ __(_)
 / /_\// /_/ / /  | |      GHC Interactive, version 6.7.20070213, for Haskell 98.
/ /_\\/ __  / /___| |
\____/\/ /_/\____/|_|      Type :? for help.

ghc-6.7.20070213: --interactive can't be used with -prof, -ticky, or -unreg.
Usage: For basic information, try the `--help' option.

Extremely similar messages are seen with 6.6 and 6.4.2. IMO the message should list -debug.

Change History (6)

comment:1 Changed 10 years ago by igloo

Milestone: 6.6.2

This comes from:

when (notNull (filter (/= WayThreaded) (wayNames dflags))
      && isInterpretiveMode cli_mode) $
   do throwDyn (UsageError
                "--interactive can't be used with -prof, -ticky, or -unreg.")

We should really have a function to print out the flag of a way name so we can just give the flag we have a problem with, but I can't see how WayUser_* come into existence. Should they be removed? Should they be refactored into WayUser Letter or WayUser Char?

There's also the problem that -smp and -threaded both result in the same flag. I guess we could make the string be "-threaded (or -smp)".

comment:2 Changed 10 years ago by simonmar

Resolution: fixed
Status: newclosed

Fixed (the error message is slightly less odd).

comment:3 Changed 9 years ago by simonmar


comment:4 Changed 8 years ago by simonmar

Architecture: UnknownUnknown/Multiple

comment:5 Changed 8 years ago by simonmar

Operating System: UnknownUnknown/Multiple

comment:6 Changed 7 years ago by simonmar

difficulty: Easy (1 hr)Easy (less than 1 hour)
Note: See TracTickets for help on using tickets.