aboutsummaryrefslogtreecommitdiff
path: root/db.c
diff options
context:
space:
mode:
authorTom Smeding <tom.smeding@gmail.com>2020-10-03 21:30:57 +0200
committerTom Smeding <tom.smeding@gmail.com>2020-10-03 21:30:57 +0200
commit08b2de406a45f98cc2b46a35719f4c9d1a87c1b5 (patch)
tree0c8b8cdfd2fbdab0cb630574e7572319e14a7c90 /db.c
parentd096bb626f8dd78b6ba1ac9c2d19e567cb88827e (diff)
ssh/tomsg_clientlib: Fix stuck-data bug in tomsg_next_event
The issue was that I have too many buffering layers. The bug occurred when the sshnc layer had received some amount of data, some of which (but not all of which) was passed on to tomsg_clientlib via sshnc_maybe_recv in receive_more_data. If the data that _was_ passed on did not constitute a full event, tomsg_clientlib did not ask for more data from the sshnc layer; it would only get received the next time there was actual data on the _socket_, at which point poll(2) would ensure the whole chain gets looped through another time.
Diffstat (limited to 'db.c')
0 files changed, 0 insertions, 0 deletions