|
From: João M. S. S. <joa...@gm...> - 2019-08-20 10:49:11
|
> Some of your earlier reports related to this issue were in 2017 and 2018. > valgrind often releases a new version approximately yearly. I have observed the error a few weeks ago (maybe a month ago), so I don't think it's a change in Valgrind's version. > You should: > 1) File a bug report, and post here a link to the bug report. Yes, I tried to create a reproducer by defining huge arrays but did not observe the error. That's when I tried to check the original code again. > 2) Attach to the bug report the source code for a reproducible test case. > Please use C language. If Ada, then be EXPLICIT about your build tools and recipe. Yes, I tried to create the test case in C but could not originate the error. > IF YOU DO NOT DO THOSE TWO THINGS, THEN YOUR COMPLAINT LIKELY WILL BE FORGOTTEN AND/OR IGNORED. I thank you for you work and time. And I can assure you that I have put lots of effort in this issue already, and was not planning not to create a bug report. I always create issue reports when I find them in software, that's the least I can do. As I said, I was trying to create the report, but couldn't. I then thought I had come up with a different error, that's why I reported it here. I don't know if it's an error in Valgrind or our code, so I thought I could discuss it here before. It seems an error during Ada's elaboration. João M. S. Silva |