[postgis-users] runtime problems on Solaris

strk at refractions.net strk at refractions.net
Tue Jun 14 02:04:05 PDT 2005


On Mon, Jun 13, 2005 at 04:52:12PM -0700, James Marca wrote:
...
> At first, we thought it might be a 32 bit/64 bit library problem, but
> that doesn't seem to be the case---ldd shows that the library is
> linked against only 64 bit libraries, and the debugger seems to show
> only 64 bit libraries are being loaded.

I think it can still be a 32/64bit issue

> We were able to make the db crash while tracing the process and got
> this:
> 
> 27725:  stat("/testbed/tools/lib/libc.so.1", 0xFFFFFFFF7FFF9070) Err#2 ENOENT
> 27725:  stat("/usr/lib/64/libc.so.1", 0xFFFFFFFF7FFF9070) = 0
> 27725:  stat("/testbed/tools/lib/sparcv9/libgcc_s.so.1", 0xFFFFFFFF7FFF9070) = 027725:  munmap(0xFFFFFFFF7D300000, 8192)                = 0
> 27725:  brk(0x10078DAD0)                                = 0
> 27725:  brk(0x100791AD0)                                = 0
> 27725:      Incurred fault #6, FLTBOUNDS  %pc = 0xFFFFFFFF7E200770
> 27725:        siginfo: SIGSEGV SEGV_MAPERR addr=0x100792000
> 27725:      Received signal #11, SIGSEGV [default]
> 27725:        siginfo: SIGSEGV SEGV_MAPERR addr=0x100792000

mmm... does the trace stop there ? 
Can you try a backtrace from gdb ?

--strk;



More information about the postgis-users mailing list