On Tue, Mar 10, 2015 at 06:36:42PM -0700, Alan Irwin wrote: > On 2015-03-03 17:09-0800 Alan W. Irwin wrote: > > >I think valgrind would report a serious issue like invalid read > >regardless of command-line options so I think the best summary of the > >situation is valgrind reports invalid reads with epa_built Qt 5.3.1 > >and 5.3.2 and does not report such issues with Ubuntu-built (and > >patched) Qt5 5.3.0. > > > >So thanks to your report my working hypothesis now is that the > >configuration of the epa_built Qt5 is somehow to blame here even > >though there are no warnings about the configuration options that I > >use in the Qt5 build log. > > > >My next step is I am going to download the Qt5 build configuration > >used by Debian testing and/or Ubuntu to see if I can spot some key > >configuration option that epa_build is missing for Qt5.3.x. > > Hi Andrew: > > The short story is that step did not work. > > Here is the longer version of the story with a request for two > additional tests (one short one long) by you at the end. > > If you have access to Debian testing, it would be great if you > repeated the valgrind test with their binary version of Qt5 (5.3.2) > which is very much closer to my epa_built version. And if you have a > spare couple of hours of cpu on a Debian testing platform, it would > also be extremely interesting to see if the epa_built version of Qt5 > did not have any memory management issues on Debian testing since if > that proved to be the case I could write this off to Debian stable > issues (i.e., the current working hypothesis) and sleep better at > night. :-) > > Meanwhile, if you can think of anything else I should try with the > epa_built version of Qt5 on Debian stable, please let me know.
I'm also stumped! I'll try building in my Debian unstable pbuilder environment and report back. This is as close as I can get and should (hopefully) help isolate the problem. Andrew ------------------------------------------------------------------------------ Dive into the World of Parallel Programming The Go Parallel Website, sponsored by Intel and developed in partnership with Slashdot Media, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials and more. Take a look and join the conversation now. http://goparallel.sourceforge.net/ _______________________________________________ Plplot-devel mailing list Plplot-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/plplot-devel
