[GRASS5] d.legend and d.out.png

[Moritz Lennert]

Glynn Clements said:
[...]
>
> The next step is to try to debug the child process. Try running
> d.what.vect but don't interact with it. Use "ps" to check whether the
> child process ($GISBASE/etc/form/form) is still running at this point.
> If it is, try attaching to it with gdb, e.g.
>
> 	$ gdb $GISBASE/etc/form/form
> 	> attach <pid>
>
> where <pid> is the PID of the etc/form/form process.
>
> Or use "strace -p <pid>".

Ok, the form process appears once I click on the map, not before. When
everything works fine I can see the form process appear normally. When
d.what.vect doesn't work (i.e. no reaction after the first click) a
defunct form process appears:

$ ps -A | grep form
 5820 pts/27   00:00:00 form <defunct>

This disappears when d.what.vect terminates silently after the second
left-click. Next time around it reappears but with a different pid.

When I try to attach in gdb or use strace -p I get:

(gdb) attach 5849
Attaching to process 5849
ptrace: Op&#65533;ration non permise.

and

$ strace -p 5849
attach: ptrace(PTRACE_ATTACH, ...): Operation not permitted

be it as normal user or as root.

> Although, I have a strong suspicion that the ultimate solution will be
> to scrap the form library. It doesn't even compile for me, it doesn't
> work for you and, in four days of discussing this, I've yet to hear
> any comments from either of the people who've actually worked on it
> (Alex and Radim).

But v.digit seems to use the library as well, or ?

>
> At the very least, I think that plain-text (i.e. -x) should be the
> default, and the use of the form library should require an explicit
> switch.

d.what.vect -x does work perfectly all the time.

Moritz