|
From: Paulo J. M. <po...@so...> - 2006-11-18 16:25:24
|
Thank you for both your replies. In fact, the problem is that it seems really confusing the amount of errors produces by valgrind. In the beginning: ==23293== Warning: client switching stacks? SP change: 0xBEABDB4C --> 0xBE396A00 ==23293== to suppress, use: --max-stackframe=7500108 or greater Is this important? First error is: ==23293== Invalid write of size 4 ==23293== at 0x804D0F6: smtparse() (smtlib-parser.cc:1355) ==23293== Address 0xBEABDB18 is on thread 1's stack This is : int yytoken = 0; This is bison generated code. How can this line contain an invalid write? Am I doing something wrong? I'm running valgrind: valgrind --leak-check=yes program args... I just go through the first 10 invalid writes reported and they all refer to bison generated code. Any ideas on this? Regards, -- Paulo Jorge Matos - pocm at soton.ac.uk http://www.personal.soton.ac.uk/pocm PhD Student @ ECS University of Southampton, UK |