Modify to properly use unsigned offset for fseek 00/316700/1 accepted/tizen_unified_x_asan accepted/tizen/unified/20241218.085933 accepted/tizen/unified/x/20241218.212029 accepted/tizen/unified/x/asan/20250113.002234
authorSangYoun Kwak <sy.kwak@samsung.com>
Mon, 16 Dec 2024 08:10:32 +0000 (17:10 +0900)
committerSangYoun Kwak <sy.kwak@samsung.com>
Tue, 17 Dec 2024 06:07:08 +0000 (15:07 +0900)
commit9f53067a75931cdb9e46dbbb5a2783277fab88fe
treef57a16dd6133667c1f5526fd672929b93d0a83bf
parentad96f77804df9f7734d0521dc00432cc8550047d
Modify to properly use unsigned offset for fseek

The fseek gets second parameter(offset) as long type. Since the size of
the long type is different depends on the architecture(32/64-bits), any
offset value which type is greater than long should be treated with
care.
To resolve this issue, fseek_offset_u64 function is created and used.
Also, offset values which are used in fseek_offset_u64 are re-typed
properly.

Change-Id: Ic213744ad866a8d4533a8016d59c96703eecc226
Signed-off-by: SangYoun Kwak <sy.kwak@samsung.com>
script/postlinker.c