NetworkInterfaceASIO does not always initialize messageId and responseTo

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Done
    • Priority: Major - P3
    • 3.1.9
    • Affects Version/s: None
    • Component/s: Networking
    • None
    • Fully Compatible
    • ALL
    • Platform A (10/09/15)
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      found with valgrinding the stress test.

      we initialize the messageId in messageFromRequest(), but in some cases we manually create a message (e.g. the LegacyRequest used for sending isMasters) and do not go through messageFromRequest(). In that case the messageId will be uninitialized. Also, responseTo() was always uninitialized. We should initialize it to 0.

            Assignee:
            Adam Midvidy (Inactive)
            Reporter:
            Adam Midvidy (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: