Closed byzhang closed 9 years ago
Yes, lwan closes stdin. I don't remember where but it's in lwan.c; just look for calls to close().
It make nvcc pass after commenting close stdin. Is the closing necessary?
Not strictly necessary. It's just closed because it's not used, and that's a file descriptor that can be used for something else.
Do you want to remove it? I can make a pull request if you prefer.
Sorry for replying this so late!
Yes, feel free to make a PR moving the close(stdin)
to the lwan
executable, away from the library.
A handler is calling NVCC to compile some cuda code, and NVCC failed with such error:
The nvcc command is
I checked kernel.cu exists (which created by ofstream in the handler as well) and such command succeeded when I ran it in console. I heard about nvcc unconditionally closs fds 0/1, does lwan already closes 0/1 before calling the handler? Can you show me the code so I can try to comment out and verify whether it's the reason?