Dear Joseph,
You can simply stop your application with ctr-c,
Wt will catch this, and properly shut down.
There should be no memory leaks in Wt or asio,
so these suppression files are not necessary.
You might find one reported error in zlib related to uninitialized memory,
but you can avoid this error by running your Wt app with the option
--no-compression.
Kind regards,
Pieter
2009/6/17 Joseph VanAndel <[email protected]>
> I'm trying to use valgrind to examine dynamic memory usage of my Wt
> based application. I'm using the built-in http server. As you know,
> valgrind is most useful when you get the program to exit normally, so
> all destructors get called.
>
> What's the best way of shutting down a Wt application cleanly?
>
> Any other suggestions on using valgrind with Wt?
>
> Has anyone built valgrind suppression files for memory leaks inside Wt
> or the asio library?
>
>
> ------------------------------------------------------------------------------
> Crystal Reports - New Free Runtime and 30 Day Trial
> Check out the new simplified licensing option that enables unlimited
> royalty-free distribution of the report engine for externally facing
> server and web deployment.
> http://p.sf.net/sfu/businessobjects
> _______________________________________________
> witty-interest mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/witty-interest
>
------------------------------------------------------------------------------
Crystal Reports - New Free Runtime and 30 Day Trial
Check out the new simplified licensing option that enables unlimited
royalty-free distribution of the report engine for externally facing
server and web deployment.
http://p.sf.net/sfu/businessobjects
_______________________________________________
witty-interest mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/witty-interest
