apr-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jeff Trawick <traw...@attglobal.net>
Subject Re: warnings with APR_USE_PROC_PTHREAD_SERIALIZE
Date Mon, 02 Jul 2001 17:29:52 GMT
Cliff Woolley <cliffwoolley@yahoo.com> writes:

> On 2 Jul 2001, Jeff Trawick wrote:
> 
> > > We didn't catch this part, though.  The apr_lock_t is pcalloc'ed just
> > > prior to calling create_lock().  Do we really need to do this?  If so,
> > > feel free to add it in...
> >
> > no prob, but sanity check the reasoning:
> >
> > the app may need to know when the pthread handle vs. the int handle is
> > being used, thus the storing of -1 in the int handle and the NULL in
> > the pthread handle
> 
> Makes sense to me.  All you should have to do is set the -1 (the NULL is
> implicit from the pcalloc).  Right?

you bet...  (though if the app doesn't know what is going on (i.e.,
which kind of lock it was gonna get) then the -1 probably won't help
much :)  at least they'll get EBADF instead of screwing up the
standard input descriptor)

-- 
Jeff Trawick | trawick@attglobal.net | PGP public key at web site:
       http://www.geocities.com/SiliconValley/Park/9289/
             Born in Roswell... married an alien...

Mime
View raw message