Hi Mathi,
I'll explain you the endian problem on an example.
Let's say that we have a SaNameT string of size 400 (which is in hexadecimal
0x190). Type of size_t is 64 bits (8 bytes)
On little endian system, 400 bytes is represented in memory as
90 01 00 00 00 00 00 00
On big endian system, 400
Hi Mathi,
The latest patch has replaced "memcpy" by using "=".
Thanks,
Minh
diff --gita/osaf/libs/common/ntfsv/ntfsv_mem.c
b/osaf/libs/common/ntfsv/ntfsv_mem.c
--- a/osaf/libs/common/ntfsv/ntfsv_mem.c
+++ b/osaf/libs/common/ntfsv/ntfsv_mem.c
@@ -1
Hi,
Could you point out the endianness problem that is mentioned in the review
request
Thanks,
Mathi.
- minh.c...@dektech.com.au wrote:
> osaf/libs/common/ntfsv/Makefile.am |1 +
> osaf/libs/common/ntfsv/include/ntfsv_mem.h |7 +
> osaf/libs/common/ntfsv/ntfsv_enc_dec.c
osaf/libs/common/ntfsv/Makefile.am |1 +
osaf/libs/common/ntfsv/include/ntfsv_mem.h |7 +
osaf/libs/common/ntfsv/ntfsv_enc_dec.c | 37 --
osaf/libs/common/ntfsv/ntfsv_mem.c | 151 +++-
4 files changed, 175 insertions(+), 21 deletions(-)