cellular-infrastructure
/
libsmpp34
mirror of https://gerrit.osmocom.org/libsmpp34
9
0
Fork 0
Code Issues Releases Wiki Activity
libsmpp34/def_frame/replace_sm.frame

11 lines
495 B
Plaintext
Raw Normal View History

initial import of libsmpp34-1.10
2012-11-07 07:32:31 +00:00
C_OCTET( instancia, message_id, 65 );
U08( instancia, source_addr_ton, str_addr_ton );
U08( instancia, source_addr_npi, str_addr_npi );
C_OCTET( instancia, source_addr, 21 );
C_OCTET( instancia, schedule_delivery_time, 17 );
C_OCTET( instancia, validity_period, 17 );
U08( instancia, registered_delivery, valueDec_08 );
U08( instancia, sm_default_msg_id, valueDec_08 );
U08( instancia, sm_length, valueDec_08 );
Fix Out of bounds compilation warning in OCTET8 The code in OCTET8 implementation assumes the len is placed inside the byte preceding the memory buffer, which is true for the defined cases. However, it creates a compilation warning. Better pass the value directly from the struct field rather than playing addr games. this way we also assert we require to explicitly pass the len. Fixes lots of warning like the one below: /home/pespin/dev/sysmocom/bin/../git/libsmpp34/src/smpp34_unpack.c: In function ‘smpp34_u npack’: /home/pespin/dev/sysmocom/bin/../git/libsmpp34/src/smpp34_unpack.c:147:14: warning: array subscript is above array bounds [-Warray-bounds] lenval = *((inst par) - 1);\ ^~~~~~~~~~~~~~~~~ /home/pespin/dev/sysmocom/bin/../git/libsmpp34/def_frame/submit_sm.frame:18:2: note: in e xpansion of macro ‘OCTET8’ OCTET8( instancia, short_message, 254 ); ^~~~~~ Change-Id: Id110f4e977c3becdb44cf5492c372e530ea51551
2017-09-15 18:09:19 +00:00
OCTET8( instancia, short_message, 254, instancia sm_length );