https://bugs.kde.org/show_bug.cgi?id=492348
--- Comment #5 from jo.al...@outlook.com <jo.al...@outlook.com> --- (In reply to Sam James from comment #4) > For what it's worth, some advice when making these reports (as a maintainer, > but not of Valgrind): > * Don't rely on screenshots. It has a certain smell but also, not everyone > can even see screenshots (e.g. screenreader users). > * Don't file multiple bugs if they're based on a tool. File one, mention you > have more, and ask how the project wants you to proceed. It might be that > there's information they need you to provide so you can make the other > reports better (avoids needless roundtrips). > * Include clear instructions as to how to reproduce it both with the tool > _and ideally without_ (analyse the issue a bit please, don't just say "my > tool found X"). Ah, thank you for that! I will keep that in mind. It was more like these bug reports I made for each Valgrind product; each had its unique issue that I analyzed. As for the screenshots, they were an intuitive medium for showing the differences, and I can share the individual reports if needed. Mainly, I'd like to remedy the situation I encountered or obtain insights into my observations so I don't put as much information into reproducing the issue if what I observed was perhaps expected. -- You are receiving this mail because: You are watching all bug changes.
