cannot read BUFR message if sections total length differs message's
Bug #619404 reported by
vanh souvanlasy
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| libECBUFR |
Fix Committed
|
Low
|
vanh souvanlasy | ||
Bug Description
When the total of all section's encoded length is different than the length of BUFR message as encoded in section 0,
as found in some badly encoded messages.
S0.length + S1.length + S2.length + S3.length + S4.length + S5.length < Total length of BUFR message set in Section 0
The bufr_read_message() function is unable to adapt and read the message anyway,
even if it contains all valid data but filled at the end by unused spaces, that is when the BUFR message is longer than it should be.
| Changed in libecbufr: | |
| assignee: | nobody → vanh souvanlasy (vanh-souvanlasy) |
| status: | New → In Progress |
| importance: | Undecided → Low |
| milestone: | none → 0.8.2b4 |
Revision history for this message
| vanh souvanlasy (vanh-souvanlasy) wrote | #1 |
| Changed in libecbufr: | |
| status: | In Progress → Fix Committed |
To post a comment you must log in.
Fixed with rev. 136 in trunk