Age | Commit message (Collapse) | Author | Files | Lines |
|
Will not harm anyone, is only used for rare short (2byte) relative pointers, and
relative_rap_convert is always 0 so far (as all init functions using struct
ndr_pull will zero the struct).
Guenther
|
|
These were causing thousands of warnings on solaris8
|
|
relative_short is like relative but instead of having the offset coded on 4 bytes
it's coded on 2 bytes. Such things happen in GET_DFS_REFERAL messages.
Signed-off-by: Stefan Metzmacher <metze@samba.org>
|
|
The default enum in NDR63 is 32 bits, not 16 bits. We need a uint1632
type to get the alignment right.
|
|
This is the type used for a variable that is 32 bits for NDR32 and 64
bits for NDR64
|
|
NDR64 has a 'trailing gap' alignment, which aligns the end of a
structure on the overall structure alignment.
This explains the discrepancy we had with the RPC-SAMR test and NDR64
|
|
This fixes the problem with samr UserInfo16 when NDR64 is enabled
|
|
This allows for easier implementation of the NDR32/NDR64 split
|
|
This adds NDR64 support for the push functions in libndr
|
|
Jeremy.
|
|
This only does pull, but it is useful for w2k8-r2 <-> w2k8-r2 ndrdump
usage, which is always 64bit.
|
|
Signed-off-by: Jelmer Vernooij <jelmer@samba.org>
|
|
|
|
cc: "../librpc/ndr/ndr_basic.c", line 572: warning 604: Pointers are not assignment-compatible.
Apparently in_addr.s_addr is not compatible to uint32_t, maybe a 32-bit signed
int.
|
|
Jeremy.
|
|
Jeremy.
|
|
|