Hi,

I checked the submitted information, the email address is correct. 
Thank you very much!

best regards
Mingxiang Lu


-----邮件原件-----
发件人: Waldemar Brodkorb <w...@openadk.org> 
发送时间: Thursday, October 31, 2024 7:41 PM
收件人: lumingxiang (操作系统开发部/NingOS, RD) <lu.mingxi...@h3c.com>
抄送: Waldemar Brodkorb <w...@openadk.org>; devel@uclibc-ng.org; zhangchun 
(操作系统开发部/NingOS, RD) <zhang.ch...@h3c.com>
主题: Re: [uclibc-ng-devel] 回复: 回复: 回复: 回复: TLS memory-leak with dlopen

Hi,

which mailaddress you wanted? I used your first patch and just extended it.

best regards
 Waldemar

Lumingxiang wrote,

> Hi,
> I apologize for not updating the patch and responding to the email promptly, 
> as I've been quite busy lately. 
> Could you please update the patch's author information to include my name and 
> email addrerss? This is very important for both me and my company.
> 
>  best regards
>  Lu mingxiang
> 
> -----邮件原件-----
> 发件人: Waldemar Brodkorb <w...@openadk.org>
> 发送时间: Thursday, October 31, 2024 4:51 PM
> 收件人: lumingxiang (操作系统开发部/NingOS, RD) <lu.mingxi...@h3c.com>
> 抄送: Waldemar Brodkorb <w...@openadk.org>; devel@uclibc-ng.org; 
> zhangchun (操作系统开发部/NingOS, RD) <zhang.ch...@h3c.com>
> 主题: Re: [uclibc-ng-devel] 回复: 回复: 回复: TLS memory-leak with dlopen
> 
> Hi,
> 
> sorry for your duplicate work. I didn't hear back from you and started to 
> extend your patch which now is pushed.
> 
> Sorry.
> 
> But my patch is really similar to yours.
> 
> best regards
>  Waldemar
> 
> Lumingxiang wrote,
> 
> > Hi,
> > 
> > Certainly. Please refer to the attached file for the extended patch 
> > applicable to all architectures using NPTL. It has been verified on both 
> > x86 and mips64 architectures.
> > 
> > best regards
> > Lumingxiang
> > 
> > -----邮件原件-----
> > 发件人: Waldemar Brodkorb <w...@openadk.org>
> > 发送时间: Tuesday, October 15, 2024 7:40 PM
> > 收件人: lumingxiang (操作系统开发部/NingOS, RD) <lu.mingxi...@h3c.com>
> > 抄送: Waldemar Brodkorb <w...@openadk.org>; devel@uclibc-ng.org; 
> > zhangchun (操作系统开发部/NingOS, RD) <zhang.ch...@h3c.com>
> > 主题: Re: [uclibc-ng-devel] 回复: 回复: TLS memory-leak with dlopen
> > 
> > Hi,
> > 
> > okay, thanks for the hint. I could reproduce the issue.
> > 
> > Unfortunately the patch is x86_64 specific. Would you be able to extend the 
> > patch for all architectures using NPTL?
> > 
> > best regards
> >  Waldemar
> > 
> > Lumingxiang wrote,
> > 
> > > 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 <w...@openadk.org>
> > > 发送时间: Monday, September 30, 2024 11:15 PM
> > > 收件人: lumingxiang (操作系统开发部/NingOS, RD) <lu.mingxi...@h3c.com>
> > > 抄送: Waldemar Brodkorb <w...@openadk.org>; devel@uclibc-ng.org; 
> > > zhangchun (操作系统开发部/NingOS, RD) <zhang.ch...@h3c.com>
> > > 主题: Re: [uclibc-ng-devel] 回复: TLS memory-leak with dlopen
> > > 
> > > Hi,
> > > Lumingxiang wrote,
> > > 
> > > > Hi,
> > > > Waldemar Brodkorb,
> > > >
> > > > > Is it possible to sent a git format-patch -s maybe as attachment?
> > > >  Certainly, please find the attachment.
> > > 
> > > Okay, thanks.
> > > 
> > > > >Do you have example code to reproduce the issue?
> > > > Yes, please see the attached example code. The two source files are 
> > > > compiled into a shared object and an application respectively.
> > > > Instructions for compiling them can be found in the first lines of the 
> > > > files.
> > > 
> > > 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?
> > > 
> > > > >Furthermore can you subscribe to the mailinglist, I had to manually 
> > > > >pass your mail.
> > > > Of course, I have already subscribed to the mailing list.
> > > 
> > > 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!
> > > _______________________________________________
> > > devel mailing list -- devel@uclibc-ng.org To unsubscribe send an 
> > > email to devel-le...@uclibc-ng.org
> 
> 
> > _______________________________________________
> > devel mailing list -- devel@uclibc-ng.org To unsubscribe send an 
> > email to devel-le...@uclibc-ng.org
> 
> _______________________________________________
> devel mailing list -- devel@uclibc-ng.org To unsubscribe send an email 
> to devel-le...@uclibc-ng.org
_______________________________________________
devel mailing list -- devel@uclibc-ng.org
To unsubscribe send an email to devel-le...@uclibc-ng.org

Reply via email to