FinishDeliverReject
    XMLWordPrintable

    Details

      Description

      There are some problems with memory leaks according to valgrind. But I think you cannot fix the errors related to dlopen, so I removed them from the output

      I start the Signer Engine from one terminal windows and stop it from another.

      rickard@fou:~/opendnssec$ valgrind --leak-check=full --show-reachable=yes ods-signerd -vvvv -d

      ==511== Invalid read of size 1
      ==511== at 0x41A3156: pthread_mutex_destroy (pthread_mutex_destroy.c:28)
      ==511== by 0x80505C3: engine_config_cleanup (cfg.c:256)
      ==511== by 0x8050C01: parent_cleanup (engine.c:237)
      ==511== by 0x8050CF3: engine_cleanup (engine.c:945)
      ==511== by 0x8052563: engine_start (engine.c:908)
      ==511== by 0x804CDCC: main (ods-signerd.c:163)
      ==511== Address 0x446a9a0 is 72 bytes inside a block of size 84 free'd
      ==511== at 0x402265C: free (vg_replace_malloc.c:323)
      ==511== by 0x80505B8: engine_config_cleanup (cfg.c:255)
      ==511== by 0x8050C01: parent_cleanup (engine.c:237)
      ==511== by 0x8050CF3: engine_cleanup (engine.c:945)
      ==511== by 0x8052563: engine_start (engine.c:908)
      ==511== by 0x804CDCC: main (ods-signerd.c:163)

      ==511== Invalid read of size 4
      ==511== at 0x41A315C: pthread_mutex_destroy (pthread_mutex_destroy.c:28)
      ==511== by 0x80505C3: engine_config_cleanup (cfg.c:256)
      ==511== by 0x8050C01: parent_cleanup (engine.c:237)
      ==511== by 0x8050CF3: engine_cleanup (engine.c:945)
      ==511== by 0x8052563: engine_start (engine.c:908)
      ==511== by 0x804CDCC: main (ods-signerd.c:163)
      ==511== Address 0x446a9a4 is 76 bytes inside a block of size 84 free'd
      ==511== at 0x402265C: free (vg_replace_malloc.c:323)
      ==511== by 0x80505B8: engine_config_cleanup (cfg.c:255)
      ==511== by 0x8050C01: parent_cleanup (engine.c:237)
      ==511== by 0x8050CF3: engine_cleanup (engine.c:945)
      ==511== by 0x8052563: engine_start (engine.c:908)
      ==511== by 0x804CDCC: main (ods-signerd.c:163)

      ==511== Invalid write of size 4
      ==511== at 0x41A3168: pthread_mutex_destroy (pthread_mutex_destroy.c:33)
      ==511== by 0x80505C3: engine_config_cleanup (cfg.c:256)
      ==511== by 0x8050C01: parent_cleanup (engine.c:237)
      ==511== by 0x8050CF3: engine_cleanup (engine.c:945)
      ==511== by 0x8052563: engine_start (engine.c:908)
      ==511== by 0x804CDCC: main (ods-signerd.c:163)
      ==511== Address 0x446a9a0 is 72 bytes inside a block of size 84 free'd
      ==511== at 0x402265C: free (vg_replace_malloc.c:323)
      ==511== by 0x80505B8: engine_config_cleanup (cfg.c:255)
      ==511== by 0x8050C01: parent_cleanup (engine.c:237)
      ==511== by 0x8050CF3: engine_cleanup (engine.c:945)
      ==511== by 0x8052563: engine_start (engine.c:908)
      ==511== by 0x804CDCC: main (ods-signerd.c:163)

      ==511== 24 bytes in 1 blocks are definitely lost in loss record 2 of 11
      ==511== at 0x4022AB8: malloc (vg_replace_malloc.c:207)
      ==511== by 0x4102504: xmlNewMutex (in /usr/lib/libxml2.so.2.6.31)
      ==511== by 0x4101E96: xmlInitGlobals (in /usr/lib/libxml2.so.2.6.31)
      ==511== by 0x80524FD: engine_start (engine.c:838)
      ==511== by 0x804CDCC: main (ods-signerd.c:163)

      ==511== 32 bytes in 1 blocks are definitely lost in loss record 4 of 11
      ==511== at 0x4022AB8: malloc (vg_replace_malloc.c:207)
      ==511== by 0x422167F: strdup (strdup.c:43)
      ==511== by 0x80681C7: se_strdup (se_malloc.c:122)
      ==511== by 0x8050A9E: engine_config (cfg.c:78)
      ==511== by 0x805251B: engine_start (engine.c:844)
      ==511== by 0x804CDCC: main (ods-signerd.c:163)

        Attachments

          Activity

            People

            Assignee:
            matthijs Matthijs Mekking
            Reporter:
            rickard Rickard Bellgrim
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved: