Le 22.10.03, Ben Collins a tapoté :
| > I'm not very familiar with compilers internals but (I once made
| > a code-generator, that's all) but how can a double negative can
| > happen ?
|
| It is basically this:
|
| fprintf(asm_file, "\tsave\t%sp, -%d, %sp\n", size_of_stack);
|
| So the first negative is hardcoded (because the stack decreases down
| always) and the second one is just the result of SSIZE_MAX plus some
| (registering saving, etc), which overflows to a negative value.
Got it :)
| > | If you need that much (I can't see that you would), then malloc it.
| >
| > I don't need that much, in fact. I just need to ensure that what
| > is send from one side of a client/server connection is fully
| > received at the other side...
|
| Then probably a 1024 byte buffer, and a loop to read/process it until
| it's all read. You'd have to make sure the connection was non-blocking
| though.
I'm a bit reserved about using non-blocking sockets : I don't like
them very much... I'll find a way to finish my program :)
Again, thank you for all.
I think we can close the bug... How should this be done ?
Thomas
--
BOFH excuse #433:
Error: one bad user found in front of screen.
