| 12345678910111213141516171819202122232425262728293031323334353637383940414243444546474849 |
- Known bugs in bsd-games and bsd-games-non-free
- ==============================================
- I know of the following bugs in bsd-games and bsd-games-non-free;
- there is no need to report them if you come across them, but fixes are
- welcome.
- General
- =======
- Some games may not handle signals (especially resizing) properly.
- Handling signals properly means in a way conforming to ISO C and
- POSIX.1: no async-unsafe functions may be used in a signal handler if
- the signal could have interrupted an async-unsafe function, and any
- variable of static storage duration assigned to must be of type
- volatile sig_atomic_t. (See adventure for an example of proper
- handling.)
- Some games may not check for errors when they should, or may return
- inappropriate exit statuses.
- Some games may have arbitrary limits that they should not have.
- Specific games
- ==============
- Under some circumstances, hunt fails to start the hunt daemon if one
- is not already running. In general, hunt needs thorough testing by
- someone willing to investigate and fix bugs; at present hunt should be
- considered unsupported and probably broken. OpenBSD has a
- substantially improved version that should be imported/merged.
- Saving in monop is completely broken. Since it assumes it can save by
- writing out the whole data space from 0 to sbrk(0) and read it in to
- restore, it may not be easy to fix. See NetBSD PR bin/8247.
- Gomoku can use 16 megabytes or more of memory. (This is reported (not
- by me) as NetBSD PR 3126.)
- Joseph S. Myers
- jsm@polyomino.org.uk
-
- Local Variables:
- mode: text
- End:
|
