Moritz
This issue has been with GRASS 5.7 for over a year. There was a thread
discussing what might be causing this a few weeks back and I almost thought
it was going to be solved. But I guess not. This is why I've gone to
d.what.vect -x in the GUI. It would be nice to get this fixed as it is a
very handy way to update attribute values on a case by case basis.
Michael
On 9/22/04 3:14 PM, "grass5-request@grass.itc.it"
<grass5-request@grass.itc.it> wrote:
I only get a form process when d.what.vect works. When it doesn't work
(i.e. silently dies after two clicks), I never see the form process come
up, so I can't attach to it.When d.what.vect works, I can attach to the form process in gdb, but then
I get no reaction from GRASS anymore until I detach in gdb.
I can send you the results of a strace -p <form pid> during a successful
session with d.what.vect. But I guess this won't help ?Moritz
______________________________
Michael Barton, Professor & Curator
School of Human Diversity and Social Change
Arizona State University
Tempe, AZ 85287-2402
USA
voice: 480-965-6262; fax: 480-965-7671
www: http://www.public.asu.edu/~cmbarton