<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<font size="-1"><font face="Arial">Thanks all for your help. <br>
<br>
We found two versions of libproj and two of GDAL. This was due
to PostGIS pulling in newer versions.<br>
<br>
PostGIS came from a repository and mapserver was compiled. We
are currently trying to figure out the best way to resolve this.<br>
<br>
One other question; Is the old php mapscript and new swig </font></font><font
size="-1"><font face="Arial"><font size="-1"><font face="Arial">php</font></font>
mapscript mutually exclusive? In other words, do we build
MapServer with one or the other? That is my guess.<br>
<br>
Thanks,<br>
<br>
</font></font>
<div class="moz-signature"><b>Worth Lutz</b><br>
<br>
<br>
</div>
<div class="moz-cite-prefix">On 4/16/2021 6:37 PM, Even Rouault
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:369ff727-3a8d-c0ff-e7d7-69a86a310bb7@spatialys.com">
<br>
<blockquote type="cite">Not sure. I would also take a look inside
your /cgi-bin/ dir and execute: ldd mapserv (and look for any
conflicts with libs) but that's an awful guess, not easy to see
(but I've been here before with PROJ/GeoTIFF/Spatialite lib
conflicts, in this case I'm not sure what lib).
<br>
</blockquote>
<br>
I strongly concur with Jeff's suggestion of using ldd mapserv.
Segmentation fault after the end of a plain & simple "mapserv
-v" really smells a binary that links to 2 versions of the same
lib, and clashes during deallocation of static variables (although
I would expect it to also crash in all situations, but behaviour
might be quite unprectible). And the usual suspects are indeed the
ones listed by Jeff.
<br>
<br>
<br>
</blockquote>
<br>
</body>
</html>