diff options
| author | kundatipradeep <35292742+kundatipradeep@users.noreply.github.com> | 2019-04-15 06:58:06 +0530 |
|---|---|---|
| committer | ssugiura <39760799+ssugiura@users.noreply.github.com> | 2019-04-15 10:28:06 +0900 |
| commit | 376bf6c1750d8d1c6bb1a5abc73e5b081d7b7825 (patch) | |
| tree | e7669c95c4a0b4eb4348ffa2e3acb21048e8218b /README.md | |
| parent | 9e5723b75937892e12e68bb2f18f5751ce3d458d (diff) | |
| download | DLT-daemon-376bf6c1750d8d1c6bb1a5abc73e5b081d7b7825.tar.gz | |
Size of Resend buffer less than or equal to DLT_USER_BUF_MAX_SIZE res… (#116)
* Size of Resend buffer less than or equal to DLT_USER_BUF_MAX_SIZE results in Memory corruption.
As older version of DLT DLT_USER_RESENDBUF_MAX_SIZE is [DLT_USER_BUF_MAX_SIZE + 100] which contains space for extra headers, where as in DLT 2.18 the resend buffer is bound to DLT_USER_BUF_MAX_SIZE which results in memory corruption in dlt_buffer_read_block when the size of the data is more than DLT_USER_BUF_MAX_SIZE.
Reason for not using "DLT_USER_RESENDBUF_MAX_SIZE" during dynamic memory allocation of resend buffer is as user has got the feasibility to alter the DLT_USER_BUF_MAX_SIZE using the environmental variables the resend buffer in any scenario to be greater then dlt_user.log_buf_len to accommodate the extra headers.
Diffstat (limited to 'README.md')
0 files changed, 0 insertions, 0 deletions