messages encoded with section 2 content are unreadable
Bug #759973 reported by
cpb
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
libECBUFR |
Fix Committed
|
Medium
|
vanh souvanlasy |
Bug Description
If you actually encode a message containing Section 2 data, the result is unreadable (to both LibECBUFR and MetManager and maybe others).
Will commit a test case.
Changed in libecbufr: | |
importance: | Undecided → Medium |
To post a comment you must log in.
Running test_section2 under a debugger suggests the read is looking for section 5 about 4 bytes short of the actual location, which suggests section 2 is too short.