[GRASS5] v.out.ascii: Segmentation fault

[Markus Neteler]

On Wed, Dec 01, 2004 at 05:32:38PM +1300, Hamish wrote:
> > > 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).
> 
> As Glynn pointed out a few weeks ago, as a security precaution Debian's
> xterm does not export $LD_LIBRARY_PATH to child processes.

Oh, didn't see that message. Why do people continue to ask then :-)

Is there any solution desired for Debian (e.g. use of another terminal)?

...
> Also I suspect a lot of these problems come from people using the
> grass.itc.it linux (but not debian) binaries and then libraries not
> being where the binaries expect them to be.

With "people" you mean Debian users?
The amount of complaints about the grass.itc.it linux binaries is not
that high (of course I can stop the job).
 
> Only problem I get is d.what.vect in form mode rarely exiting on the
> first click (without an error). Haven't been able to reproduce this with
> the debugger running. Next time I see it I'll do "echo $?" at least.
> Never had the "works once" d.what.vect problem.

AFAIK the "d.what.vect first click problem" is only related to Debian
and MacOSX. So users of these platforms will have to debug.

Markus