Menu
▾
▴
plplot-devel
|
From: Andrew R. <ar...@ge...> - 2001-11-28 05:16:27
|
For Jo=E3o and Alan in particular, In the last snapshot I took from the CVS I found X20C is now totally broken. I get SIGFP errors (ie floating point of some sort). It does not matter which driver I use either. Is this also visiting the linux versions, or just my DJGPP build ? Also, I got a lot of minor conflicts between plcore.c, plimage.c and definitions in plplotp.h. I did my own patch to plplotp.h to try and circumvent it and let me compile, but not knowing which is correct (ie plcore.c or plplotp.h) i didn't want to commit my changes. Oh, Alan, in case you are interested, I just added support for different line widths in the GD driver ! - Andrew |
|
From: Alan W. I. <ir...@be...> - 2001-11-28 06:06:53
|
Andrew, I haven't committed any of my x20c changes to CVS yet. However, because of your problems with the latest CVS version, I just did a fresh checkout, configure, and build of that version to make sure Joao's very recent changes (mostly from Allesandro) and your recent gd driver changes work on my machine. In short, everything with xwin and psc seems to work, but now there is trouble for the gd driver so that (e.g.) every x??c example I tried with -dev png produces a segfault. So I suggest you review your recent gd changes to see if that is the source of our common trouble. Good night for now, and I will do some more testing of gd tomorrow if you haven't found the solution by then. Alan email: ir...@be... phone: 250-727-2902=09FAX: 250-721-7715 snail-mail: Dr. Alan W. Irwin Department of Physics and Astronomy, University of Victoria, P.O. Box 3055, Victoria, British Columbia, Canada, V8W 3P6 __________________________ Linux-powered astrophysics __________________________ On Wed, 28 Nov 2001, Andrew Roach wrote: > For Jo=E3o and Alan in particular, > In the last snapshot I took from the CVS I found X20C is now totally > broken. I get SIGFP errors (ie floating point of some sort). It does not > matter which driver I use either. Is this also visiting the linux version= s, > or just my DJGPP build ? > > Also, I got a lot of minor conflicts between plcore.c, plimage.c and > definitions in plplotp.h. I did my own patch to plplotp.h to try and > circumvent it and let me compile, but not knowing which is correct (ie > plcore.c or plplotp.h) i didn't want to commit my changes. > > > Oh, Alan, in case you are interested, I just added support for different > line widths in the GD driver ! > > - Andrew > > > _______________________________________________ > Plplot-devel mailing list > Plp...@li... > https://lists.sourceforge.net/lists/listinfo/plplot-devel > |
|
From: Andrew R. <ar...@ge...> - 2001-11-28 11:43:37
|
>In short, everything with xwin and psc seems to work, >but now there is trouble for the gd driver so that (e.g.) every >x??c example I tried with -dev png produces a segfault. >So I suggest you review your recent gd changes to see if that is the > >Good night for now, and I will do some more testing of gd tomorrow if >you haven't found the solution by then. I only actually added about 8 new lines to the driver, so the differences are minimal, and there would seem to be little to go wrong there. On DJGPP I had to change the linking order from the earlier versions of GD (ie 1.8.4) to get GD 2.0.1 to work with anything without crashing. That happened with or without my changes to gd.c (ie the older version of gd.c linked against the libgd.a 2.0.1 caused the same problems with crashes). Try linking the maths library AFTER all the GD and GD dependent libraries. At present I believe it is linked in before them. This change made a big difference for my build, though logic and good coding suggests it should not have. Perhaps it might fix yours ? - Andrew |
|
From: Alan W. I. <ir...@be...> - 2001-11-28 14:27:43
|
iOn Wed, 28 Nov 2001, Andrew Roach wrote: > I only actually added about 8 new lines to the driver, so the differences > are minimal, and there would seem to be little to go wrong there. Hmmm. I just tried a test with the old version of gd.c, and all the segfaults go away. With the new gd.c I also overrode GD2_VERS to be 1 and the result was no segfaults. However, if I left it at 2 (i.e., actually compile your 3 calls to gdImageSetThickness(dev->im_out, pls->width)), the segfaults come back. Either there is something wrong with libgd 2.0.1 or more likely dev->im_out or pls->width are not properly set when you make these calls. (Recall our previous Linux segfault problem with gd was caused by a subtle undefined argument problem.) Until you can find the answer, I have overriden GD2_VERS in the interest of keeping -dev png operational on CVS head. Alan |
|
From: Andrew R. <ar...@ge...> - 2001-11-29 01:58:48
|
Hello, First, back to the original SEGFP errors I was getting with X20c. I have compiled x20c WITHOUT any GD driver at all, and I still get the same SEGFP errors, so it isn't anything new introduced in the GD driver changed. I know it is related to the plimage command, but where in it I don't know. >> I only actually added about 8 new lines to the driver, so the differences >> are minimal, and there would seem to be little to go wrong there. > >Hmmm. I just tried a test with the old version of gd.c, and all the >segfaults go away. With the new gd.c I also overrode GD2_VERS to be 1 and >the result was no segfaults. However, if I left it at 2 (i.e., actually >compile your 3 calls to gdImageSetThickness(dev->im_out, pls->width)), the >segfaults come back. Either there is something wrong with libgd 2.0.1 or more >likely dev->im_out or pls->width are not properly set when you make these >calls. pls->width should be set from plplot, and is ok. I don't think the problem can be there. dev->im_out could have a problem, but that will sadly go back to GD somewhere. I think something is wrong with libgd 2.0.1 - it is listed on the gd web site as an "unstable beta", and there is a warning in the makefile that linking order can be significant. We knew that from the very first incarnation of the GD driver anyway, but at least for DJGPP, the linking order has changed AGAIN *sigh*. The last STABLE version of GD is 1.8.4. I strongly suspect the problem is in GD. >Until you can find the answer, I have overriden GD2_VERS in the interest of >keeping -dev png operational on CVS head. Probably a good idea, but there is sadly little I can do, because unfortunately (fortunately?) it works on my machine and I can't replicate your problem :-( Wekl actually I CAN replicate it, but I can also FIX it by changing the linking order, and making sure the maths library links AFTER libgd.a, libpng.a, and libjpeg.a . Did you try reordering the linking ? One other thought. Are you 100% sure that you are linking against the 2.0.1 library and not the 1.8.? library ? You might have the headers for GD 2 but the library for GD 1 - that would probably cause an error like this. - Andrew |
Thanks for helping keep SourceForge clean.
X