coredump of ..., write failed: errno 14

[Stuart Henderson]

I've seen this a lot recently (14 = EFAULT)

2017-07-13T16:05:57.935Z symphytum /bsd: coredump of Xorg(62706), write failed: errno 14
2017-07-13T16:05:57.993Z symphytum /bsd: coredump of chrome(46797), write failed: errno 14
2017-07-13T16:05:58.081Z symphytum /bsd: coredump of vi(26461), write failed: errno 14
2017-07-13T16:05:58.124Z symphytum /bsd: coredump of ksh(24425), write failed: errno 14

partial coredumps get saved but they aren't usable with gdb..
This is with kern.nosuidcoredump=2, there's plenty of space in /var/crash.

Any ideas?

[Theo de Raadt]

Post by Stuart Henderson
I've seen this a lot recently (14 = EFAULT)
2017-07-13T16:05:57.935Z symphytum /bsd: coredump of Xorg(62706), write failed: errno 14
2017-07-13T16:05:57.993Z symphytum /bsd: coredump of chrome(46797), write failed: errno 14
2017-07-13T16:05:58.081Z symphytum /bsd: coredump of vi(26461), write failed: errno 14
2017-07-13T16:05:58.124Z symphytum /bsd: coredump of ksh(24425), write failed: errno 14
partial coredumps get saved but they aren't usable with gdb..
This is with kern.nosuidcoredump=2, there's plenty of space in /var/crash.

I believe this happens when then user address space of the application is
changed, ie a shared library has gotten smaller in some aspect. Then the
write fails because the memory is not there. It is not about disk space,
14 is EFAULT.