>> >changes the layout of the structure, so you'd have to add padding to
>> >structures that lack it.
>> if they don't have padding, they do not work right even now.
>I.e., a structure
> struct foo {
> u_int32_t a;
> u_int8_t b;
> u_int32_t c;
> };
>won't work as a packet format description - you have to use
> struct foo {
> u_int32_t a;
> u_int8_t b;
> u_int8_t pad[3];
> u_int32_t c;
> };
>? If so, are there any structures of the sort that won't work?
i mean, if there's any structure decl which depends on automatic
padding now, the struct definition will be interpreted differently
on 64bit and 32bit arch (= doesn't work correctly).
itojun
-
This is the TCPDUMP workers list. It is archived at
http://www.tcpdump.org/lists/workers/index.html
To unsubscribe use mailto:tcpdump-workers-request@;tcpdump.org?body=unsubscribe
