Well, I *think* the destroy functions I added to the .l files for the old flex case will clean up everything correctly. What I mean is we will correctly clean up when using new flex (valgrind clean). We still recommend using new flex (2.5.33 or newer recommended) but we will continue to support old flex because of Redhat's decision to include old flex in RHEL 5.
From: devel-bounces_at_[hidden] [devel-bounces_at_[hidden]] on behalf of Paul Hargrove [phhargrove_at_[hidden]]
Sent: Thursday, December 06, 2012 5:20 PM
To: Open MPI Developers
Subject: Re: [OMPI devel] [OMPI svn] svn:open-mpi r27580 - in trunk: ompi/mca/btl/openib ompi/mca/btl/wv ompi/mca/coll/ml opal/util/keyval orte/mca/rmaps/rank_file
What does this mean with respect to "clean up" and old flex?
Have you simply conceded that old flex will leak memory?
On Thu, Dec 6, 2012 at 4:16 PM, Hjelm, Nathan T <hjelmn_at_[hidden]<mailto:hjelmn_at_[hidden]>> wrote:
Done. We now clean up correctly in new flex while having support for old flex.
Paul H. Hargrove PHHargrove_at_[hidden]<mailto:PHHargrove_at_[hidden]>
Future Technologies Group
Computer and Data Sciences Department Tel: +1-510-495-2352
Lawrence Berkeley National Laboratory Fax: +1-510-486-6900