[CWB] [cwb:bugs] #40 Memory leak check on cwb utils and cqp

[Andrew Hardie]

In the Perl modules: this should be doable by adding a single switch when "make" runs. This should insert a variable $ValgrindCmd into Config.pm (empty string by default, with the flag, "valgrind --leak-check=yes "

This can be triggered when running Makefile.PL:

    perl Makefile.PL --with-valgrind

Then, modify CWB/lib/CWB.pm where the application "full pathnames" are set. Lines 177 ff

For each one, add CWB::Config::$ValgrindCmd before $BinDir. 

We also want C compilation done by the Perl installer to use the GCC flags.  I think this involves WriteMakefile().


     OPTIMIZE => ($with_valgrind ? "-Og" : "-O"),


In CWB itself: very simple check on WITH_VALGRIND. 



---

** [bugs:#40] Memory leak check on cwb utils and cqp**

**Status:** open
**Group:** TODO-3.5
**Created:** Fri Sep 03, 2010 10:56 AM UTC by Andrew Hardie
**Last Updated:** Thu Apr 08, 2021 12:52 AM UTC
**Owner:** Andrew Hardie


We need to run CQP and the CWB tools through Valgrind on Linux, in order to see whether we have big memory leaks, buffer overflows or looming segmentation faults.


---

Sent from sourceforge.net because cwb at sslmit.unibo.it is subscribed to https://sourceforge.net/p/cwb/bugs/

To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/cwb/admin/bugs/options.  Or, if this is a mailing list, you can unsubscribe from the mailing list.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://liste.sslmit.unibo.it/pipermail/cwb/attachments/20210408/d63de4ea/attachment.html>