Uploaded image for project: 'Kudu'
  1. Kudu
  2. KUDU-677

Enforce that client-side allocations are paired with client-side deallocations

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Open
    • Trivial
    • Resolution: Unresolved
    • M5
    • None
    • client
    • None

    Description

      There is ample evidence that if dynamic libraries allocate a resource, they should provide a way to deallocate those resources. The kudu client library doesn't do this, and it should.

      This isn't a problem while both the library and its application dynamically link libstdc+, as they're guaranteed to use the same libstdc+ and wind up with the same implementations for new/delete. We only need to start worrying when one of the two statically links libstdc++, as that opens the door for different versions to be used across the client module boundary.

      More directly, this may become an issue when internal client code starts using C+11; that's when we'd use static linking to hide our C+11 dependency from third party applications.

      Attachments

        Activity

          People

            Unassigned Unassigned
            adar Adar Dembo
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated: