Mailing-List: contact dev-help@apr.apache.org; run by ezmlm
Precedence: bulk
Received-SPF: pass (athena.apache.org: domain of carenas@sajinet.com.pe
 designates 76.74.239.193 as permitted sender)
Date: Thu, 5 Aug 2010 14:34:21 +0000
From: Carlo Marcelo Arenas Belon <carenas@sajinet.com.pe>
To: dev@apr.apache.org
Subject: Re: undefined behaviour from apr_pollset_create
Message-ID: <20100805143421.GA30585@sajinet.com.pe>
References: <20100804141704.GA22728@sajinet.com.pe>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20100804141704.GA22728@sajinet.com.pe>
User-Agent: Mutt/1.5.18 (2008-05-17)

On Wed, Aug 04, 2010 at 02:17:04PM +0000, Carlo Marcelo Arenas Belon wrote:
> 
> apr_pollset_create in apr 0.9 used to keep that pointer unchanged (NULL)
> for that case and by looking at the code/behaviour from newer versions
> it would seem that it gets allocated an apr_pollset_t* always, resulting
> on an application bug, where an infinite loop was created while polling
> repeatedly and empty pollset.

after further investigation this resulted to be a wrong assumption on my
part, the pollset pointer inside the opaque apr_pollset_t structure is
indeed NULL in 0.9, but considering that it is opaque anyway, its status
shouldn't matter and therefore this should be instead considered just as
undocumented behaviour then.

Carlo