Re: [Log4cplus-devel] MacOS X champion for log4cplus

[Václav Z. <vha...@gm...>]

On 1 June 2012 14:41, Jeremy C. Reed wrote:
> On Fri, 1 Jun 2012, V?clav Zeman wrote:
>
>> I am looking for MacOS X champion for the log4cplus project. While
>> log4cplus is fairly portable and should work with little to no changes
>> even on MacOS X, I cannot actually ensure that it does because I have
>> no access to any MacOS X installation. Your task would be to
>> (occasionally) test log4cplus and report bugs and suggest fixes to
>> keep log4cplus working on the MacOS X platform.
>
> BIND 10 tests on MacOS X automatically (using Clang++ and G++) over 2500
> times since I enabled it in January 2011. I think some of our developers
> use Mac OS X as primary platform. We have over 50 unit tests focusing on
> our logging plus higher level feature tests using the logging output. (I
> can point you to details later.)
>
> Do you have any log4cplus test suite you'd like us to also run?
I am assuming that since BIND 10 uses it, the basic facilities work.
What might need some checking is threads and thread local storage.
Could you please check tests/thread_test does something sensible and
that tests/ndc_test's output is the same (minus difference in thread
ID) on both Linux and MacOSX?

>
> Our only problem noticed on MacOS X only is the ^@ null characters
> sometimes found in the output. http://bind10.isc.org/ticket/1629 We will
> do a temporary instrumented version that detects the Ctrl-@ and aborts
> so we can track down where this comes from. (This is work is targetted
> for our current two week sprint.)
I have seen the ticket but I could not think of a reason for such behaviour.

>
> (By the way, my reply is not to suggest others don't consider the
> original request. Yes please someone be the MacOSX champion.)

-- 
VZ