[Mapserver-users] RE: Linux segmentation problem

[Hatcher Matthew]

Hi,
All the libraries are found and look to be in the places I expected them to
be. Anybody more seasoned at looking at this kind of stuff than me see any
problems?

Matt.


ldd mapserv
        libgd.so.2 => /usr/local/lib/libgd.so.2 (0x40029000)
        libjpeg.so.62 => /usr/lib/libjpeg.so.62 (0x4007a000)
        libfreetype.so.6 => /usr/lib/libfreetype.so.6 (0x40098000)
        libpng12.so.0 => /usr/lib/libpng12.so.0 (0x400e9000)
        libz.so.1 => /usr/lib/libz.so.1 (0x4010c000)
        libproj.so.0 => /usr/local/lib/libproj.so.0 (0x4011a000)
        libgdal.1.1.so => /usr/local/lib/libgdal.1.1.so (0x4014d000)
        libcurl.so.2 => /usr/lib/libcurl.so.2 (0x403a4000)
        libssl.so.4 => /lib/libssl.so.4 (0x403c7000)
        libcrypto.so.4 => /lib/libcrypto.so.4 (0x403fc000)
        libdl.so.2 => /lib/libdl.so.2 (0x404ed000)
        libresolv.so.2 => /lib/libresolv.so.2 (0x404f0000)
        libgssapi_krb5.so.2 => /usr/kerberos/lib/libgssapi_krb5.so.2
(0x40503000)
        libkrb5.so.3 => /usr/kerberos/lib/libkrb5.so.3 (0x40516000)
        libk5crypto.so.3 => /usr/kerberos/lib/libk5crypto.so.3 (0x40574000)
        libcom_err.so.3 => /usr/kerberos/lib/libcom_err.so.3 (0x40584000)
        libpthread.so.0 => /lib/tls/libpthread.so.0 (0x40586000)
        libm.so.6 => /lib/tls/libm.so.6 (0x40593000)
        libstdc++.so.5 => /usr/lib/libstdc++.so.5 (0x405b6000)
        libc.so.6 => /lib/tls/libc.so.6 (0x42000000)
        libXpm.so.4 => /usr/X11R6/lib/libXpm.so.4 (0x40669000)
        libX11.so.6 => /usr/X11R6/lib/libX11.so.6 (0x40678000)
        libungif.so.4 => /usr/lib/libungif.so.4 (0x40757000)
        libgcc_s.so.1 => /lib/libgcc_s.so.1 (0x4075f000)
        /lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x40000000)

-----Original Message-----
From: Vincent Schut [mailto:schut at sarvision.com]
Sent: 13 May 2003 13:37
To: Hatcher Matthew; 'Björn Platzen';
'mapserver-users at lists.gis.umn.edu'
Subject: Re: [Mapserver-users] Linux segmentatio n problem


Matt,

If you want to be sure about the shared libraries, run 'ldd mapserv' (and
'ldd 
php_mapscript.so' if you want to use mapscript).

Regards,
Vincent Schut.

On Tuesday 13 May 2003 14:00, Hatcher Matthew wrote:
> Hi Bjoern,
>
> Thanks for your suggestion, but unfortunately, shp2img runs fine without
> any errors!
>
> I don't think mapserv is actually getting as far as reading the map file,
> because I get a segmentation fault whether I specify a valid map file or
> not. I'm pretty sure it's not that it can't find some shared libraries, as
> they normally complain that they are missing when you do "mapserv -v".
>
> Any more ideas?!
>
> Matt.
>
>
> -----Original Message-----
> From: Björn Platzen [mailto:bplatzen at sosnetz.de]
> Sent: 13 May 2003 12:47
> To: Hatcher Matthew; 'mapserver-users at lists.gis.umn.edu'
> Subject: Re: [Mapserver-users] Linux segmentation problem
>
>
> Hi Matthew,
>
> > However, if I pass any parameters at all, be they in mapserver, WMS
> > or WFS format, I get an internal server error. The error log says
> > only "premature end of script", and if I run mapserv at the command
> > line by passing a QUERY_STRING here, I get "segmentation fault".
>
> I had a similar problem and could find out what went wrong the shp2img
> program, that was compiled with mapserver. Run it on a shell with your
> mapfile (e.g. shp2img -m mapfile.map -o output.png) and see, if there
> are any errors. If yes, I think, that the same errors will happen using
> the mapserv CGI.
>
> hth,
>
> Bjoern.

-- 
______________________________________
Vincent Schut
Sarvision B.V.
Wageningen, The Netherlands
www.sarvision.com
The Information contained in this E-Mail and any subsequent correspondence
is private and is intended solely for the intended recipient(s).
For those other than the recipient any disclosure, copying, distribution,
or any action taken or omitted to be taken in reliance on such information
is prohibited and may be unlawful.

Emails and other electronic communication with QinetiQ may be monitored.
Calls to our Customer Contact Centre may be recorded for quality control,
regulatory and monitoring purposes.