We have config parameter BugcheckAbort, making it possible not to try to continue server operation after bugcheck (which is hardly possible in most cases), but abort() at once, providing useful debug information - core file. But in many cases system is setup by default not to dump core at all. Users often have troubles, moreover setup using OS tools may differ for classic/super cases.
In order to avoid such problems, it's better to make firebird to as much as possible to create core file on BUGCHECK.
Added code, making firebird server to change working directory to (as for the rule) writable location (/tmp) and setting soft core file size limit equal to hard limit. In release version it's done only when BugcheckAbort is true. In devel version it's done always.
Submitted by: @AlexPeshkoff
We have config parameter BugcheckAbort, making it possible not to try to continue server operation after bugcheck (which is hardly possible in most cases), but abort() at once, providing useful debug information - core file. But in many cases system is setup by default not to dump core at all. Users often have troubles, moreover setup using OS tools may differ for classic/super cases.
In order to avoid such problems, it's better to make firebird to as much as possible to create core file on BUGCHECK.
Commits: 547eb36 b50399c c59d5b9 52c9aca
The text was updated successfully, but these errors were encountered: