https://bugs.kde.org/show_bug.cgi?id=458915
--- Comment #25 from Philippe Waroquiers <philippe.waroqui...@skynet.be> --- (In reply to Libor Peltan from comment #24) > You will probably need to run the test several time until it reproduces. It > may also happen on some machines that it does never reproduce. For me, it > easily reproduces on my laptop, but hardly on a powerful server. Thanks for the detailed instructions. I was able to reproduce the bug, happens more or less 1 on 5 trials. I will further work on this time permitting (valgrind is a week-end activity, so only a few hours from time to time). One question: the test outputs valgrind messages in the file 'valgrind' and outputs the valgrind debug output in stderr. This setup is very special, I would like to have both outputs in the same file. I have not seen where is the piece of code that really launches valgrind and makes these 2 separate files (I even do not too much understand how this is done, as valgrind messages and debug output are normally both written on the same fd). Is there an easy change to the test framework that would ensure all the output is either in stderr or valgrind file ? Thanks Philippe -- You are receiving this mail because: You are watching all bug changes.
