Activity
From 02/11/2018 to 03/12/2018
03/02/2018
- 10:33 AM Bug #4525 (New): Destructing a ChronoSync socket object shuts down the face
- Currently the ChronoSync socket class accepts a reference to a Face object. I think this is intended to support using...
02/13/2018
- 04:15 PM Bug #4140: ChronoSync sendSyncData can result in trying to send content exceeding the size of the packet
- Two related commits:
- https://gerrit.named-data.net/#/c/4535/
- https://gerrit.named-data.net/#/c/4536/
- 11:45 AM Bug #4140: ChronoSync sendSyncData can result in trying to send content exceeding the size of the packet
- If we don't, then may be we wouldn't see the error. On testbed, we ARE adding ndnlp headers now.
- 11:25 AM Bug #4140: ChronoSync sendSyncData can result in trying to send content exceeding the size of the packet
- If we don't set any tags on the data packet then the lpPacket should be empty and we would be sending a Data packet w...
02/12/2018
- 07:33 PM Bug #4140: ChronoSync sendSyncData can result in trying to send content exceeding the size of the packet
- Ashlesh Gawande wrote:
> Okay, the user specified limit will replace `MAX_NDN_PACKET_SIZE` while comparing to syncR... - 07:32 PM Bug #4140: ChronoSync sendSyncData can result in trying to send content exceeding the size of the packet
- The testbed size has grown considerably. Also, having separate chronosync prefixes for NAME and COORDINATE inflated t...
- 06:18 PM Bug #4140: ChronoSync sendSyncData can result in trying to send content exceeding the size of the packet
- Would it be possible to post the ChronoSync log before the crash from this node and other nodes?
When we used NSync ... - 04:50 PM Bug #4140: ChronoSync sendSyncData can result in trying to send content exceeding the size of the packet
- Okay, the user specified limit will replace MAX_NDN_PACKET_SIZE while comparing to syncReply size?
- 03:17 PM Bug #4140: ChronoSync sendSyncData can result in trying to send content exceeding the size of the packet
- The solution is incomplete, as it didn't provision for NDNLPv2 headers, resulting in the following error
```
1518... - 10:32 AM Bug #4496 (Closed): ABI changes when ChronoSync compiled with/without debug mode
02/11/2018
- 07:46 PM Bug #4495: Strange buffer overflow / random crash of chronosync::Socket related to ndn::InMemoryStorage
- We should tell that Crytpo++ and Boot.Log developers who are quite abusing this :)
- 07:41 PM Bug #4495: Strange buffer overflow / random crash of chronosync::Socket related to ndn::InMemoryStorage
- The lesson: don’t use preprocessor conditionals to add or remove fields in headers unless the defines are in a common...
- 02:09 PM Bug #4495: Strange buffer overflow / random crash of chronosync::Socket related to ndn::InMemoryStorage
- Alex Afanasyev wrote:
> Davide discovered a changeable ABI when compiled with `_DEBUG` define.
Specifically, clas... - 01:57 PM Bug #4495: Strange buffer overflow / random crash of chronosync::Socket related to ndn::InMemoryStorage
- Davide discovered a changeable ABI when compiled with `_DEBUG` define. When compiling the snippet using `-D_DEBUG=1`...
- 09:47 AM Bug #4495: Strange buffer overflow / random crash of chronosync::Socket related to ndn::InMemoryStorage
- valgrind confirms the same memory error <https://travis-ci.org/yoursunny/TravisCI-temp/builds/340186679>
- 08:52 AM Bug #4495: Strange buffer overflow / random crash of chronosync::Socket related to ndn::InMemoryStorage
- I'm able to reproduce this bug on Ubuntu 14.04.
<https://travis-ci.org/yoursunny/TravisCI-temp/builds/340164777> - 05:39 PM Bug #4496 (Code review): ABI changes when ChronoSync compiled with/without debug mode
- https://gerrit.named-data.net/4529
- 02:00 PM Bug #4496 (Closed): ABI changes when ChronoSync compiled with/without debug mode
- There are several `ifdef` in header files that alter ABI depending on defines, which is a (or the) cause for #4495 an...
Also available in: Atom