25 Jul
2006
25 Jul
'06
7:03 a.m.
"Ge van Geldorp" <ge(a)gse.nl> wrote:
Why is this required? Is that due to asserts in server/request.c, open_master_socket() ?
Exactly.
What exactly size is required then to avoid an assert?
Is changing 'int' to 'long' a better fix?
Perhaps. It would become
struct request_max_size { long pad[10]; int pad1[6]; };
then, which seems just as arbitrary.
No, I meant to make it irrespective to 32 or 64-bit compilation, i.e. look like: struct request_max_size { long pad[16]; }; -- Dmitry.