Testers wanted: reentrant resolver
Brian F. Feldman
green at FreeBSD.org
Sat Feb 21 16:38:16 PST 2004
Daniel Eischen <eischen at vigrid.com> wrote:
> On Fri, 20 Feb 2004, Brian F. Feldman wrote:
>
> > Daniel Eischen <eischen at vigrid.com> wrote:
> >
> > > > Could you take a look at my test program (that I put in src/tools/) to see
> > > > if I made any pthreading errors?
> > >
> > > Where in src/tools?
> >
> > It's in src/tools/regression/gaithrstress.
>
> Yes, it looks fine to me.
>
> One other thing about your patch, probably minor. Since h_error
> is only used for the main thread now, multithreaded applications
> that haven't been recompiled will still be referencing it
> instead of the new function. This would seem to break the ABI,
> right? These older applications will pick up the wrong h_error.
That's right; applications that use the mostly-deprecated h_errno API will
have to be recompiled if they want to get the right error codes. I don't
see a way around that, so I'm not worried about it -- and I don't think any
application that doesn't do its own big giant lock around all
gethostbyname() calls should be using h_errno; if it's using getaddrinfo(),
the correct API for accessing errors is there.
--
Brian Fundakowski Feldman \'[ FreeBSD ]''''''''''\
<> green at FreeBSD.org \ The Power to Serve! \
Opinions expressed are my own. \,,,,,,,,,,,,,,,,,,,,,,\
More information about the freebsd-current
mailing list