[uclibc-ng-devel] 回复: 回复: TLS memory-leak with dlopen

Hi, Waldemar Brodkorb, I apologize for forgetting to mention earlier that Valgrind was initially unable to detect the memory leak. At first, we also used Valgrind for analysis, but it didn’t catch the memory leak. However, by monitoring memory usage with the command cat /proc/[pid]/status | grep VmRSS, we observed a continuous increase in the size of the target process. After applying the patch, this memory leakage issue was resolved. Could you please try using it? best regards Mingxiang Lu -----邮件原件----- 发件人: Waldemar Brodkorb <wbx(a)openadk.org> 发送时间: Monday, September 30, 2024 11:15 PM 收件人: lumingxiang (操作系统开发部/NingOS, RD) <lu.mingxiang(a)h3c.com> 抄送: Waldemar Brodkorb <wbx(a)openadk.org>rg>; devel(a)uclibc-ng.org; zhangchun (操作系统开发部/NingOS, RD) <zhang.chunA(a)h3c.com> 主题: Re: [uclibc-ng-devel] 回复: TLS memory-leak with dlopen Hi, Lumingxiang wrote, Okay, thanks. I tried attached code with valgrind in qemu-system-x86_64 with a uClibc-ng master system, but valgrind did not found any memleak. Furthermore I tried the code in the original bugreport, but here also no memleak is found. Any idea? Can you post the output of valgrind? Can you see the memleak? Thanks. best regards Waldemar ------------------------------------------------------------------------------------------------------------------------------------- 本邮件及其附件含有新华三集团的保密信息，仅限于发送给上面地址中列出 的个人或群组。禁止任何其他人以任何形式使用（包括但不限于全部或部分地泄露、复制、 或散发）本邮件中的信息。如果您错收了本邮件，请您立即电话或邮件通知发件人并删除本 邮件！ This e-mail and its attachments contain confidential information from New H3C, which is intended only for the person or entity whose address is listed above. Any use of the information contained herein in any way (including, but not limited to, total or partial disclosure, reproduction, or dissemination) by persons other than the intended recipient(s) is prohibited. If you receive this e-mail in error, please notify the sender by phone or email immediately and delete it!