--- Comment #8 from Giuseppe D'Angelo <dangelog@???> --- > I think it should fail if not enough disk space, but it seems it assigns the same zero page to the file several times and simply crash when copy-on-write fails. Do you have any idea how to fix this? Creating a temporary signal handler, writing data, capturing segfault seems an awkward way to handle this.
Unfortunaly yes, you need to "touch" the space (by writing into it) in order to
actually have the OS allocate it. It's in the same family of behaviors like
requesting lots of memory via malloc, which succeeds, then your program crashes
when you actually write into such memory.
You are receiving this mail because:
You are on the CC list for the bug.
This message was posted to the following mailing lists: