Date: Fri, 17 Nov 1995 02:04:02 -0800 From: David Greenman <davidg@Root.COM> To: grog@lemis.de (Greg Lehey) Cc: bmk@dtr.com, hackers@freebsd.org (FreeBSD Hackers) Subject: Re: elm problem :) Message-ID: <199511171004.CAA00915@corbin.Root.COM> In-Reply-To: Your message of "Fri, 17 Nov 95 09:45:38 %2B0100." <199511170845.JAA24499@allegro.lemis.de>
next in thread | previous in thread | raw e-mail | index | archive | help
>> I wasn't able to get it working with fcntl locking, either. I compiled
>> and installed it long before I knew of the existance of a port (one might
>> have existed, I don't know). I've always had to use flock style locking
>> - fcntl always seemed to cause the symptoms the original complaint
>> described.
>
>I've followed this up a little, and now believe that fcntl locking is
>broken. I took an elm I compiled on BSD/386 (in fact, the one I'm
>using now) and went through with gdb. The result: the system call to
>fcntl has identical parameters in each case:
>
>(gdb) p lock_info
>$1 = {
> l_type = 3,
> l_whence = 0,
> l_start = 0,
> l_len = 0,
> l_pid = 0
>}
>
>l_type is F_WRLCK, and it's calling fcntl with F_SETLK. This works as
>advertised with BSD/386, but returns with an invalid argument with
>FreeBSD in all versions I've tried recently.
>
>I haven't got any further (can somebody please tell me how to enter
>ddb from the keyboard? Something goes and messes up my keymap, so I
>can't get in after booting), but intend to do so some time soon.
If you can put together a short program to demonstrate the bug, I would be
happy to find and fix it.
-DG
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199511171004.CAA00915>