BIGEXEC Succeding with no console output


(David Robert Olsen) #1

When we run BIGEXEC, it is passing, but not printing any output other than the “success” indicator. It also is not leaking any memory, at least according to khu. Could this be a matter of allocating too much memory somewhere?


(Geoffrey Challen) #2

It’s possible that your sys_write is broken during the test.


(David Robert Olsen) #3

I am pretty sure this bug comes into effect when dynamically allocating memory in exec. As long as the test still passes locally and on test161, do we necessarily have to worry about it?


(Geoffrey Challen) #4

I’d worry about it, yes :slight_smile: