Hi!
Arie> Any hints how one could better trace the parsing process (debug Arie> the Bison parser and the relevant components within the libsmi Arie> itself). Any other suggestions?
Kang> [...] I recommend following exception handling. [...]
Arie's problem is due to memory leaks in the libsmi code. The exact reasons cannot be identified and fixed by wrapping exception handling around the libsmi calls.
Some time ago, I fixed most of the more costly leaks using Purify and dmalloc. Bill Fenner also helped a lot in fixing leaks. But, when I came to a point where I lost oversight and only minor leaks were left, I gave up, since the commonly used programs (smilint, smidump) are just oneshot tools; there were no long term processes so far where memory consumption significantly matters. (Sorry for that bad excuse! ;-))
-frank -- !! This message is brought to you via the `libsmi' mailing list. !! Please do not reply to this message to unsubscribe. To subscribe or !! unsubscribe, send a mail message to libsmi-request@ibr.cs.tu-bs.de. !! See http://www.ibr.cs.tu-bs.de/projects/libsmi/ for more information.