[Libwebsockets] valgrind under lwsws

Mario Theodoridis mario.theodoridis at regify.com
Wed Aug 23 15:39:02 CEST 2017


On 23/08/17 14:52, Andy Green wrote:
>
>
> On 08/23/2017 08:38 PM, Andy Green wrote:
>>
>> ...
>> Well... valgrind is working fine.  You have a "debug symbols for 
>> dynamically loaded library" issue, which is not actually something 
>> wrong with lws.  But it would be nice if we could get lws to print 
>> the address gdb wants.
>
> Again sorry... valgrind and gdb are somewhat different issues.
>
> This has a couple of tips worth trying...
>
> https://stackoverflow.com/questions/38218487/how-to-trace-dynamically-loaded-libraries-with-valgrind 
>
>
>  - defeat the uv_dlclose(&p->lib); on libuv.c:708 so the lib is still 
> around when valgrind runs after the main process exits
>
>  - maybe use LD_PRELOAD=<plugin.so> to load the dynamically loaded lib 
> as if it was a normal dynamic lib requirement

Awesome! Both of these approaches work.
Obviously the latter one is preferable, since it doesn't require an 
lwsws rebuild.

Thank you.

-- 
Mit Freundlichen Grüßen / Regards

Mario Theodoridis

regify GmbH
Römerstrasse 39 | D-78183 Hüfingen
Amtsgericht Freiburg HRB 709343
Telefon: +49 771 8978 4238




More information about the Libwebsockets mailing list