1) A bug in the handling of Processes with empty input or output streams.
2) An error in the function for computing quotients of algebra modules.
3) An error in computing the strongly connected components of a binary
relation in which incorrect results can be returned.
4) A "no method found" error in OrbitStabilizerAlgorithm for infinite
groups.
5) Calculation of iterated automorphism groups might stop with an error message.
6) A segmentation fault when converting length 0 compressed vectors to
larger fields
7) The output of the internal pager (see 'Pager') is no longer copied to
log files.
8) Some memory is not freed up as soon as it could be, resulting in
over-use of memory and over-large saved workspaces
9) Saving and loading a workspace using a kernel containing a
statically loaded user module (most likely a compiled GAP file)
did not work.
10) Problems with EulerianFunction for certain types of groups
Installing the bugfix. ======================
Load the zoo archive `fix4r3n2.zoo' from the bugfixes web page
http://www-gap.dcs.st-and.ac.uk/~gap/Info4/bugfixes.html
Alternatively you can find this file in the `bugfixes' directory of the
GAP4 ftp distribution.
Unpack the file in the home directory of your GAP distribution (the
directory containing the `lib' and `grp' directories) using `unzoo -x
fix4r3n2.zoo'. `unzoo' may ask you for permissions to overwrite files,
answer this with Y)es or A)ll. This will replace the erroneous files by
fixed versions.
(On a PC or a Mac you will have to copy `unzoo' in the same directory and
enter the argument line after the call to `unzoo'.)
Make sure you have write permissions when applying the fix.
This fix changes the kernel. You have to recompile by calling `make' in the
directory in which you unpacked the fix.
Windows users can find a new binary in the file `wbin4r3n2.zoo' in the
`bugfixes' directory: Extract this archive in the same place as the fix
archive to get a new `bin/gapw95.exe' file.
Macintosh users should download the file 'bin4r3n2-PPC.sit' (for PPC
machines) or 'bin4r3n2-68k.sit' (for 68k machines), from the 'bugfixes'
directory.
If you get one of these precompiled binaries you do not need to get any
precompiled binaries that would have come with earlier fixes (these old
binaries are obsolete now). Similarly, if you cannot find these binaries but
have further, newer, fixes to install check whether new binaries with these
fixes did not make the binaries of this fix obsolete.
You can remove the file `description2' afterwards.
After installing the bugfix you can test whether
the bugfix has been applied correctly by starting GAP from the `gap4r3'
directory and issuing
gap> ReadTest("tst/bugfix.tst");
+ bugfixes test
+ GAP4stones: 163
true
(The output should be like this if the bugfixes have been installed
correctly. The number of GAP4stones may vary according to your system.)
Running this test is not a necessary part of installing a bug fix, but only
serves as a confirmation that everything went well. The test might run for
a long time and GAP will not output information while running. Note that it
is not possible to run the test twice without restarting GAP and that an
interruption of the test with CTRL-C will produce lots of (harmless) error
messages.
Steve Linton September 2002
--
Steve Linton School of Computer Science &
Centre for Interdisciplinary Research in Computational Algebra
University of St Andrews Tel +44 (1334) 463269
http://www-theory.dcs.st-and.ac.uk/~sal Fax +44 (1334) 463278