Read and respond to this message at: https://sourceforge.net/forum/message.php?msg_id=3011048 By: nobody
Since you guys are no help, I thought I'd try to answer my own question ... This source of memory leaks is a well known problem when using Flex/Bison. There are several posting about this issue on the Flex/Bison mailing list, but no really good solutions. It seems that the %destructor is currently a hack that is not really ready for production code. Based on these issues, it's much easier to write your own memory allocation functions, and track all of the memory allocated to flex/bison. Periodically, or once you have finished a parse, you can explicitly free and memory that was leaked. (Still kind of a hack, but it least it will work!) Enjoy ... ______________________________________________________________________ You are receiving this email because you elected to monitor this forum. To stop monitoring this forum, login to SourceForge.net and visit: https://sourceforge.net/forum/unmonitor.php?forum_id=74807 ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ GnuWin32-Users mailing list GnuWin32-Users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/gnuwin32-users
