In most cases, the system produces informative error messages. However, there are situations where MonetDB enters an area not covered by the test suite or previous use and a segmentation fault occurs. These cases are hard to analyze outside the development lab. To isolate and resolve the issue we need at least the following information.
Send us the result of the command
mserver5 --version --dbname=<databasename>
or the equivalent using
monetdb --version <databasename>
Is the error reproducible with a small (5-10 line) script/query/program? Trim your experiment to the minimal size that demonstrates the erroneous behavior. Such a script is the best we can hope for, because it will end up in the regression testing.
In addition, follow the steps, assuming that you are logged onto the same Linux (!) machine as where the server will run:
mserver5 --dbpath="..." --set mapi_port=54321 -d10
ps -C mserver5 or
ps -al | grep mserver5
gdb mserver5 <processid>
where. It shows the context of the crash using the list command and the variables used in the context of the crash.
thr app all bt.