[GRASS5] v.out.ascii: Segmentation fault

Markus Neteler neteler at itc.it
Mon Nov 29 11:20:46 EST 2004


On Mon, Nov 29, 2004 at 05:18:03PM +0100, Jachym Cepicky wrote:
> One more thing:
> On Thu, Nov 25, 2004 at 02:01:21PM +0100, Markus Neteler wrote:
> > On Thu, Nov 25, 2004 at 01:45:00PM +0100, Jachym Cepicky wrote:
> > [...]
> > > GRASS 5.7.cvs:~ > strace v.out.ascii novy
> > > execve("/usr/local/grass-5.7.cvs/bin/v.out.ascii", ["v.out.ascii", "novy"], [/* 32 vars */]) = 0
> > > uname({sys="Linux", node="trava", ...}) = 0
> > > brk(0)                                  = 0x804b000
> > > old_mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x40017000
> > > access("/etc/ld.so.nohwcap", F_OK)      = -1 ENOENT (No such file or directory)
> > > open("/etc/ld.so.preload", O_RDONLY)    = -1 ENOENT (No such file or directory)
> > > open("/usr/local/grass-5.7.cvs/lib/tls/i686/mmx/cmov/libgrass_vect.so", O_RDONLY) = -1 ENOENT (No such file or directory)
> > > stat64("/usr/local/grass-5.7.cvs/lib/tls/i686/mmx/cmov", 0xbffff058) = -1 ENOENT (No such file or directory)
> > > open("/usr/local/grass-5.7.cvs/lib/tls/i686/mmx/libgrass_vect.so", O_RDONLY) = -1 ENOENT (No such file or directory)
> > 
> > There is something wrong. The library should go into
> >  /usr/local/grass-5.7.cvs/lib/libgrass_vect.so
> > 
> 
> GRASS 5.7.cvs:~ > locate libgrass_vect.so
> /usr/local/grass-5.7.cvs/lib/libgrass_vect.so
> /usr/src/grass/grass51/dist.i686-pc-linux-gnu/lib/libgrass_vect.so
> GRASS 5.7.cvs:~ >
> 
> Don't know, if it helps

Now I see: It's the "famous" mysterious (to me) Debian problem:

For some unknown reasons Debian users have to add to
/etc/ld.so.conf

the directory of the GRASS libs, here:
/usr/local/grass-5.7.cvs/lib

and run
ldconfig

I would like to know that solved but have no idea why Debian behaves
like this (reported earlier by other Debian/GRASS users).

It's probably related to the fact that Debian searches in
 /usr/local/grass-5.7.cvs/lib/tls/i686/mmx/
                              ^^^^^^^^^^^^^
Why this?

Of course we could add a workaround into /etc/Init.sh for
Debian but that doesn't look like a good solution to me.

Markus




More information about the grass-dev mailing list