1: Known bugs in bsd-games and bsd-games-non-free
    2: ==============================================
    3: 
    4: I know of the following bugs in bsd-games and bsd-games-non-free;
    5: there is no need to report them if you come across them, but fixes are
    6: welcome.
    7: 
    8: General
    9: =======
   10: 
   11: Some games may not handle signals (especially resizing) properly.
   12: Handling signals properly means in a way conforming to ISO C and
   13: POSIX.1: no async-unsafe functions may be used in a signal handler if
   14: the signal could have interrupted an async-unsafe function, and any
   15: variable of static storage duration assigned to must be of type
   16: volatile sig_atomic_t.  (See adventure for an example of proper
   17: handling.)
   18: 
   19: Some games may not check for errors when they should, or may return
   20: inappropriate exit statuses.
   21: 
   22: Some games may have arbitrary limits that they should not have.
   23: 
   24: Specific games
   25: ==============
   26: 
   27: Under some circumstances, hunt fails to start the hunt daemon if one
   28: is not already running.  In general, hunt needs thorough testing by
   29: someone willing to investigate and fix bugs; at present hunt should be
   30: considered unsupported and probably broken.  OpenBSD has a
   31: substantially improved version that should be imported/merged.
   32: 
   33: Saving in monop is completely broken.  Since it assumes it can save by
   34: writing out the whole data space from 0 to sbrk(0) and read it in to
   35: restore, it may not be easy to fix.  See NetBSD PR bin/8247.
   36: 
   37: Gomoku can use 16 megabytes or more of memory.  (This is reported (not
   38: by me) as NetBSD PR 3126.)
   39: 
   40: 
   41: Joseph S. Myers
   42: jsm@polyomino.org.uk
   43: 
   44: 
   45: ^L
   46: Local Variables:
   47: mode: text
   48: End: