I'm not sure if this deserves a bug report, but I'd like to pay attention to it here. CVF 6.6B (and 6.6A) generates a temporary copy of an ALLOCATABLE array on WRITE to a binary file. The following causes a stack overflow on WRITE:
PROGRAM Test INTEGER(1), ALLOCATABLE:: bits(:) ALLOCATE(bits(1100000)) !INTEGER:: bits(1100000) OPEN(11,FILE="Test.bin",FORM="Binary") WRITE(11) bits(1:1100000) CLOSE(11) END PROGRAM
Stack overflow does not occur if the array is static; it does not occur when the array triplet (1:1100000) is ommitted either.
(If you've downloaded XFTGDI from my web page, this will happen on XSaveBitmap for a moderately large bitmap)