Well, a good error message is if the server politely tells you that your ruleset (or anything out of Freeciv application) is wrong when it is and terminates. If you see a traceback ladder, it's already something that should not happen for better and probably a point to be bugtracked. If you even get segfault instead of traceback, it's just a very bad error. Alas, the code of ruleset loading has been mostly tested on a limited range of parameters that appear in the standard rulesets and out of it has dozens of holes like overflows or dangling pointers that corrupt the application's memory, and if the program survives this stage, you easily get problems afterwards. Since your ruleset is, like, very unusual and tests limits of many things, you indeed naturally get loads of segfaults.eldritch_cookie wrote: ↑Thu Jul 14, 2022 11:02 am should i report any time that i get a segmentation fault instead of a error as a bug? that happens constantly,and i am using the latest master so i thought that was expected.
Reporting bugs is not what you are obliged to do but if you can supply some clues (describe what you were doing, bring console output, ruleset files or savegames, maybe for a segfault case run your program in gdb and show the backtrace) the developers will be thankful for the help (though not necessary that they deal with the problem in any specific time).