From owner-freebsd-hackers Mon May 11 21:02:59 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA24375 for freebsd-hackers-outgoing; Mon, 11 May 1998 21:02:59 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from pluto.plutotech.com (mail.plutotech.com [206.168.67.137]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA24364; Mon, 11 May 1998 21:02:49 -0700 (PDT) (envelope-from gibbs@plutotech.com) Received: from narnia.plutotech.com (narnia.plutotech.com [206.168.67.130]) by pluto.plutotech.com (8.8.7/8.8.5) with ESMTP id WAA29568; Mon, 11 May 1998 22:02:41 -0600 (MDT) Message-Id: <199805120402.WAA29568@pluto.plutotech.com> X-Mailer: exmh version 2.0.1 12/23/97 To: Julian Assange cc: Garance A Drosihn , gibbs@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: Re: more queue.h brokenness In-reply-to: Your message of "12 May 1998 11:11:57 +1000." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 11 May 1998 21:58:55 -0600 From: "Justin T. Gibbs" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >No, by other types I meant the other queue types, e.g STAILQ/LIST. > >The definitions for TAILQ_LAST and TAILQ_PREV have changed; I'm not >sure if these new definitions have fixed the problem or not (the code >path is complex). The symptoms were that after a certain combination >of inserts and removes, TAILQ_PREV on the first element returned the >first member, rather than NULL (meaning a backwards loop through the >TAILQ never ended). When there was only one member left, TAILQ_LAST >returned NULL, rather than the first member. Before this change, TAILQ_PREV was unusable for reverse traversals in a list. It returned a pointer to the "links" area of the previous object, not the previous object. >Cheers, >Julian. -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message