On 24 Oct, I wrote:
> On 24 Oct, Eric Jacoboni wrote:
> > Hi,
> > 
> 
> I got exactly the same on my i386 1.6I with a few programs, did a ktrace of it
> to see if it actually tried to look for it. And lo' and behold, if even
> finds it. But then does something to it that I'll have to look into.
> 
>  16235 vim      CALL  open(0x4812a8c0,0,0xbfbfb280)
>  [...]
>  16235 vim      GIO   fd 2 wrote 1 bytes
> 

This was vim-gtk, when I tried to compile vim without gtk (plain vim). It did
not have that problem.

/Anders