From owner-freebsd-hackers  Fri Nov 17 02:07:37 1995
Return-Path: owner-hackers
Received: (from root@localhost)
          by freefall.freebsd.org (8.6.12/8.6.6) id CAA20825
          for hackers-outgoing; Fri, 17 Nov 1995 02:07:37 -0800
Received: from Root.COM (implode.Root.COM [198.145.90.17])
          by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id CAA20819
          for <hackers@freebsd.org>; Fri, 17 Nov 1995 02:07:32 -0800
Received: from corbin.Root.COM (corbin [198.145.90.50]) by Root.COM (8.6.12/8.6.5) with ESMTP id CAA15623; Fri, 17 Nov 1995 02:07:29 -0800
Received: from localhost (localhost [127.0.0.1]) by corbin.Root.COM (8.6.12/8.6.5) with SMTP id CAA00915; Fri, 17 Nov 1995 02:04:03 -0800
Message-Id: <199511171004.CAA00915@corbin.Root.COM>
To: grog@lemis.de (Greg Lehey)
cc: bmk@dtr.com, hackers@freebsd.org (FreeBSD Hackers)
Subject: Re: elm problem :) 
In-reply-to: Your message of "Fri, 17 Nov 95 09:45:38 +0100."
             <199511170845.JAA24499@allegro.lemis.de> 
From: David Greenman <davidg@Root.COM>
Reply-To: davidg@Root.COM
Date: Fri, 17 Nov 1995 02:04:02 -0800
Sender: owner-hackers@freebsd.org
Precedence: bulk

>> 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