[Quickfix-developers] Why does a QuickFIX process on my Redhat server not write its core file where it should?

[Bob M. <bo...@gm...>]

I have 10 C++ programs running on a Redhat 6.9 server, all using some
internally developed libraries. One of the libraries implements logging,
and keeps file descriptor 3 open for the log file. If any of the process
gets a segmentation violation signal (signal 11), a core file is produced
in /tmp, as expected according to /proc/sys/kernel/core_pattern. However, 1
process in particular does not do this. If it gets a signal 11, it writes a
core file to the log file, which becomes useless because log messages are
interleaved with the binary core information. The main thing that is
different about this process is that it uses the QuickFIX C++ library
version 1.14.3. I have the source for that library, and have searched it to
see what it might be doing to cause this. The only signal handler it
overrides is for SIGPIPE. It opens some files, but does nothing
specifically with file descriptor 3. The QuickFIX process uses about 8GB of
memory, but processes that use more memory write their core files
correctly, so I don't think it is a file size issue.

Any ideas what the QuickFIX library could be doing to cause the core file
to not go where it should, or anything else that could be doing this?
This question is also posted on stackoverflow
<https://stackoverflow.com/questions/48451149/why-does-a-quickfix-process-on-my-redhat-server-not-write-its-core-file-where-it>
.

Thanks,
Bob McNaughton