Hi Jim, On 10/11/10 18:58, Jim Idle wrote: > Keep going with valgrind, but this is either that you are releasing and then > reusing your input file or have not allocated enough memory or something > similar. Look at the output of valgrind closely as it is probably telling > you what you are doing wrong.
I am sorry to say but valgrind is not telling anyting: with valgrind the program runs OK and it just mentions that there are a lot of memory leaks which seems reasonable because I do not release anything (nor allocate allocate anything with new or malloc for that part). I also do not release or reuse the input file. Actually the program does not contain much code that is written by myself. The grammar has some calls to functions embedded that just print the thing that are recognised. And is in calling one of the 4 functions that the program crashes. I really think that there is a hidden "you should know this when you embed antlr in a library" thing that I am not aware of or that there is something else ( I don't like to shout bug :-)) I attached my valgrind log and again mention http://trac.askesis.nl/downloads/AntlrProblem.tar.bz2 in the hope that you can help me to find the problem. TIA -- Met vriendelijke groeten, Joost Kraaijeveld Askesis B.V. Molukkenstraat 14 6524NB Nijmegen tel: 024-3888063 / 06-51855277 fax: 024-3608416 web: www.askesis.nl
List: http://www.antlr.org/mailman/listinfo/antlr-interest Unsubscribe: http://www.antlr.org/mailman/options/antlr-interest/your-email-address
valgrind_17704.txt.tar.bz2
Description: application/bzip
-- You received this message because you are subscribed to the Google Groups "il-antlr-interest" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/il-antlr-interest?hl=en.
