Valgrind will crash with an assertion error: m_deduppoolalloc.c:258 (vgPlain_allocEltDedupPA): Assertion 'eltSzB <= ddpa->poolSzB' failed. when encountering a debug info string larger than 64kb. This can quite easily be reproduced when using heavily templated C++ code.
Fixed in revision 15787. Note: the fix was tested by temporarily changing the pool size to a very small value. It would be nice if you could produce a small test case which has a string > 64 Kb, so as to have a regression test for this.
Hi Philippe, I tested with the latest HEAD and it works! Thanks a lot for fixing this issue, it is greatly appreciated. Should I go ahead and close the bug or what is the workflow?
David, please provide a small test case as Philippe suggested. That would be highly appreciated!
I can try :) What would the format of a testcase be? Would a C++ code snippet be good enough?
(In reply to David Hallas from comment #4) > I can try :) What would the format of a testcase be? Would a C++ code > snippet be good enough? A small compilable testcase c++ is ok. Bonus points if the testcase consists in a single file. Thanks
Created attachment 97251 [details] Reduced test case
I have attached a reduced test case that shows the problem. I have tested with gcc-4.9.3 and clang-3.7.1 using a 64bit Linux PC. I compiled it like this: g++ -std=c++11 main.cpp -o test I also verified that the latest master fixes the problem. Let me know if there is anything else you need
(In reply to David Hallas from comment #7) > I have attached a reduced test case that shows the problem. I have tested > with gcc-4.9.3 and clang-3.7.1 using a 64bit Linux PC. I compiled it like > this: > > g++ -std=c++11 main.cpp -o test > > I also verified that the latest master fixes the problem. > > Let me know if there is anything else you need Thanks for the test case. Test added in revision 15799
So, should I go ahead and close the bug now that a testcase has been added?
(In reply to David Hallas from comment #9) > So, should I go ahead and close the bug now that a testcase has been added? Status was changed to RESOLVED/FIXED which seems to be the final status of valgrind bugs.