bug-binutils
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Bug gold/23245] New: memory leak with static link stdc++ with --no-gnu-


From: bknt814 at gmail dot com
Subject: [Bug gold/23245] New: memory leak with static link stdc++ with --no-gnu-unique at dlclose
Date: Tue, 29 May 2018 17:55:41 +0000

https://sourceware.org/bugzilla/show_bug.cgi?id=23245

            Bug ID: 23245
           Summary: memory leak with static link stdc++ with
                    --no-gnu-unique at dlclose
           Product: binutils
           Version: 2.25
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: gold
          Assignee: ccoutant at gmail dot com
          Reporter: bknt814 at gmail dot com
                CC: ian at airs dot com
  Target Milestone: ---

I static link stdc++ gcc into a dso with --no-gnu-unique to independence c++ on
old system and let the dso can be dynamic unloaded from memory so use glod and
option --no-gnu-unique. It works but a huge of memory leak if call
dlopen/dlclose a long time. for more info please look at below:

https://stackoverflow.com/questions/49992058/dlclose-cant-work-if-make-a-empty-dso-with-link-static-libstdc

https://stackoverflow.com/questions/50402314/static-link-stdc-without-stb-gnu-unique-cause-memory-leak-when-dlclose

I hope it is not a bug. But how can I fix the memory leak?

-- 
You are receiving this mail because:
You are on the CC list for the bug.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]