Peter Mueller wrote:
> using the most recent version of GAP (under UNIX), the program below
> yields [...] [an error].
This is a known bug in the routine for ConjugacyClasses in permutation
groups, which was modified from 3.2 -> 3.3. It is fixed in GAP 3.4 (which
should be out REALLY soon now :-) ).
If you get an confusing error message from deep inside, ending with ..., you
might try Backtrace(<number>) to see a longer call history. In this example
you can see, that is was initiated by ConjugacyClasses. (This obviously does
not fix the bug, but it might help seeing, what went wrong.)
I would like to take the opportunity (for example this bug has been
mentioned already several times in the Forum) to remind you of the adress
firstname.lastname@example.org, which is designed specially for
error reports: Save your co-Forum-readers from reading long error reports.