[Plplot-devel] Problem with test-drv-info a bit clearer
Hello all, I have done some tests wrt the strange error messages I got from test-drv-info yesterday. It turns out that the program is issuing an error code -1073741515 (completely nonsensical of course) when it can not find the driver - the PATH environment variable does not contain the directory containing the driver DLLs. From the source code for test-drv-info I would guess that a more proper error message should occur, but perhaps this does not work under Windows/MinGW. (Yesterday I probably made a mistake in updating the path before running make again, so that the error occurred multiple times. I will make a note on the Wiki about this.) Regards, Arjen On 2010-05-06 16:40, Arjen Markus wrote: > > On 2010-05-06 16:37, David MacMahon wrote: >> On May 6, 2010, at 7:27 , Arjen Markus wrote: >> >>> this is indeed very puzzling! I have never seen it before - and all >>> the stuff I used I have used countless times before. >>> >>> Also puzzling: why does a repeated invocation of test-drv-info via make >>> examine different drivers? It must be recording some information. >> Have you tried from a clean build tree? Sometimes after making Makefile >> changes, old build products from previous builds can cause weird >> problems because make no longer considers them but the tools make >> invokes might consider/use them. >> >> Just an idea, >> Dave >> > > Hi Dave, > > thanks, but that was not the cause: I always rebuild from scratch. > (Hm, but not just now ... I will have to re-examine this! And I need > to keep track of seemingly unimportant glitches, like the one with > the PATH I just mentioned) > > Regards, > > Arjen > > > -- > ___ > Plplot-devel mailing list > Plplot-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/plplot-devel > -- ___ Plplot-devel mailing list Plplot-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/plplot-devel
Re: [Plplot-devel] Propagation of C example changes to our other language examples is needed
On 2010-05-06 16:37, David MacMahon wrote: > > On May 6, 2010, at 7:27 , Arjen Markus wrote: > >> this is indeed very puzzling! I have never seen it before - and all >> the stuff I used I have used countless times before. >> >> Also puzzling: why does a repeated invocation of test-drv-info via make >> examine different drivers? It must be recording some information. > > Have you tried from a clean build tree? Sometimes after making Makefile > changes, old build products from previous builds can cause weird > problems because make no longer considers them but the tools make > invokes might consider/use them. > > Just an idea, > Dave > Hi Dave, thanks, but that was not the cause: I always rebuild from scratch. (Hm, but not just now ... I will have to re-examine this! And I need to keep track of seemingly unimportant glitches, like the one with the PATH I just mentioned) Regards, Arjen -- ___ Plplot-devel mailing list Plplot-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/plplot-devel
Re: [Plplot-devel] Propagation of C example changes to our other language examples is needed
On May 6, 2010, at 7:27 , Arjen Markus wrote: > this is indeed very puzzling! I have never seen it before - and all > the stuff I used I have used countless times before. > > Also puzzling: why does a repeated invocation of test-drv-info via > make > examine different drivers? It must be recording some information. Have you tried from a clean build tree? Sometimes after making Makefile changes, old build products from previous builds can cause weird problems because make no longer considers them but the tools make invokes might consider/use them. Just an idea, Dave -- ___ Plplot-devel mailing list Plplot-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/plplot-devel
Re: [Plplot-devel] Propagation of C example changes to our other language examples is needed
Hi Alan, On 2010-05-06 16:27, Arjen Markus wrote: > Hi Alan, > > this is indeed very puzzling! I have never seen it before - and all > the stuff I used I have used countless times before. > > I will try and reproduce it. > It has disappeared! The only thing I can think of that is different is the path - previously I had a PATH variable that referred to another build directory (or more accurately: the DLL subdirectory there), so at some point I had to correct that. Now I corrected it immediately. Maybe that has caused the initial failure. > As for the PostScript files: they look fine to me - there is nothing > wrong with them. > > Also puzzling: why does a repeated invocation of test-drv-info via make > examine different drivers? It must be recording some information. > Of course, it is creating a copy of the rc-files - that is the information it is using. Consider this a strange but not important incident. (I will keep it in mind for future reference) Regards, Arjen -- ___ Plplot-devel mailing list Plplot-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/plplot-devel
Re: [Plplot-devel] Propagation of C example changes to our other language examples is needed
Hi Alan, this is indeed very puzzling! I have never seen it before - and all the stuff I used I have used countless times before. I will try and reproduce it. As for the PostScript files: they look fine to me - there is nothing wrong with them. Also puzzling: why does a repeated invocation of test-drv-info via make examine different drivers? It must be recording some information. Regards, Arjen On 2010-05-06 16:22, Alan W. Irwin wrote: > > Hi Arjen: > > I presume you have done this exact test many times before on this platform. > So the question on my mind is what is different about this test compared to > your prior ones? For example, do you have the same issue for a PLplot > release that you know you have tested before on this platform? > > This test replication issue is a substantial part of the value of reporting > test results at > http://www.miscdebris.net/plplot_wiki/index.php?title=Testing_PLplot; once > you report a working test there then in future if there is some regression > you will have recorded in the table the exact revision number and the exact > platform that worked before for you. > > One other extremely puzzling thing about your report is that test-drv-info > just does a subset of what the PLplot library does with dynamic devices so > if it fails, the PLplot library should also fail to dynamically load the > device driver. So why is test-drv-info failing while the PLplot library is > (apparently) succeeding? Do the actual PLplot results you get from say the > psc device look fine in a PostScript viewer or are they blank or badly > rendered? > > Alan > __ > Alan W. Irwin > > Astronomical research affiliation with Department of Physics and Astronomy, > University of Victoria (astrowww.phys.uvic.ca). > > Programming affiliations with the FreeEOS equation-of-state implementation > for stellar interiors (freeeos.sf.net); PLplot scientific plotting software > package (plplot.org); the libLASi project (unifont.org/lasi); the Loads of > Linux Links project (loll.sf.net); and the Linux Brochure Project > (lbproject.sf.net). > __ > > Linux-powered Science > __ > -- ___ Plplot-devel mailing list Plplot-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/plplot-devel
Re: [Plplot-devel] Propagation of C example changes to our other language examples is needed
On 2010-05-06 08:58+0200 Arjen Markus wrote: > [...]in the process of testing I came across a rather strange > problem: > > (I ran on Windows XP, with the MinGW GNU compilers) > test-drv-info stops with an error of -10356462 (or something similar), > thus terminating the build. Restarting the build makes it fail again, > but now on the next device. Hi Arjen: I presume you have done this exact test many times before on this platform. So the question on my mind is what is different about this test compared to your prior ones? For example, do you have the same issue for a PLplot release that you know you have tested before on this platform? This test replication issue is a substantial part of the value of reporting test results at http://www.miscdebris.net/plplot_wiki/index.php?title=Testing_PLplot; once you report a working test there then in future if there is some regression you will have recorded in the table the exact revision number and the exact platform that worked before for you. One other extremely puzzling thing about your report is that test-drv-info just does a subset of what the PLplot library does with dynamic devices so if it fails, the PLplot library should also fail to dynamically load the device driver. So why is test-drv-info failing while the PLplot library is (apparently) succeeding? Do the actual PLplot results you get from say the psc device look fine in a PostScript viewer or are they blank or badly rendered? Alan __ Alan W. Irwin Astronomical research affiliation with Department of Physics and Astronomy, University of Victoria (astrowww.phys.uvic.ca). Programming affiliations with the FreeEOS equation-of-state implementation for stellar interiors (freeeos.sf.net); PLplot scientific plotting software package (plplot.org); the libLASi project (unifont.org/lasi); the Loads of Linux Links project (loll.sf.net); and the Linux Brochure Project (lbproject.sf.net). __ Linux-powered Science __ -- ___ Plplot-devel mailing list Plplot-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/plplot-devel
