Menu

#3251 clm: pyosaf clma stuck in decode nodeAddress

5.21.03
fixed
None
defect
clm
lib
major
False
2021-03-01
2021-01-29
No

some weird character appear after ip address

nodeAddress --> 10.0.3.101#035

That leading pyosaf clma stuck in decode node address

1 Attachments

Related

Wiki: ChangeLog-5.21.03

Discussion

  • Thien Minh Huynh

    • status: accepted --> review
     
  • Thien Minh Huynh

    • summary: clm: clma receive nodeAddress is unexpected --> clm: pyosaf clma stuck in decode nodeAddress
    • Description has changed:

    Diff:

    --- old
    +++ new
    @@ -1,2 +1,4 @@
    -some character weird appear after ip address
    +some weird character appear after ip address
     > nodeAddress  --> 10.0.3.101#035
    +
    +That leading pyosaf clma stuck in decode node address
    
     
  • Thien Minh Huynh

    • Attachments has changed:

    Diff:

    --- old
    +++ new
    @@ -0,0 +1 @@
    +clma_python.trace (93.0 kB; application/octet-stream)
    
     
  • Thien Minh Huynh

    • status: review --> fixed
     
  • Thien Minh Huynh

    commit b6be093ce58e647a32585fc5797d66b75fe06f2b (HEAD -> develop, origin/develop)
    Author: thien.m.huynh thien.m.huynh@dektech.com.au
    Date: Wed Feb 3 14:13:29 2021 +0700

    clm: use calloc instead malloc to remove garbage value [#3251]
    
    The buffer nodeAddress having the garbage value. That leading to
    pyosaf clma is stuck during decode byte-string.
    
    The fix is make sure buffer clean before stored.
    
     
  • Gary Lee

    Gary Lee - 2021-03-01
    • Milestone: 5.20.11 --> 5.21.03
     

Log in to post a comment.