log4cplus-devel — Mailing list for log4cplus developers

Re: [Log4cplus-devel] Unicode Text Logging

[vvv j. <vv...@ya...>]

Hi log4cplus Devel Team,

Thanks Václav Zeman for the detailed explanation. 


I understood that the problem is not with log4cplus library but it is the behavior of stream in c++. I will try the deriving the FileAppender and check the output or may be I change the code in log4cplus as I'm using both RollFileAppender and DailyRollFileAppender.  

Regarding the 2nd options imbue I'm using Visual Studio 2008, so need to check if that options work or not.

Thanks again to log4cplus team for giving good support.

Regards
J.Viswanath



________________________________
 From: Václav Zeman <vha...@gm...>
To: vvv jjj <vv...@ya...> 
Cc: log...@li... 
Sent: Friday, 1 June 2012 6:52 PM
Subject: Re: [Log4cplus-devel] Unicode Text Logging
 
On 31 May 2012 19:21, Václav Zeman wrote:
> On 05/31/2012 05:46 PM, vvv jjj wrote:
>> Hi log4cplus Devel Team,
>>
>> Thanks Václav Zeman.
>>
>> I gave Unicode text directly in the cpp file. (Ex: CString str =
>> _T("Ω⅓∂₤◊");)
>> The file is saved with unicode support (the default yes button when
>> Unicode file is saved in Visual Studio 2008). The configuration used
>> is Debug Unicode dynamic library.
>>[...]
I have reproduced your problem on Windows as well. The problem is
Windows problem with its code pages.

Even though you are using the Debug_Unicode (or Release_Unicode)
configuration, which means that the output stream is std::wfstream,
the output file is always using chars (not wchar_ts). If you insist on
logging characters outside of your Windows code page, then you are
unfortunately (nearly) out of luck for 1.0.4.1.

The best way to work around this for 1.0.4.1 would be to derive your
own appender from *FileAppender that you use and either (1) override
its append() member function to do, either wchar_t -> UTF-8 (or any
other translation) on the fly, or, if you can use Visual Studio 2010,
(2) imbue the underlying file stream with, e.g.,
std::codecvt_utf8<tchar, 0x10FFFF,
static_cast<std::codecvt_mode>(std::consume_header |
std::little_endian)> facet.

For trunk and 1.1.x branches you can do (2) using imbue() member
function on *FileAppender.

-- 
VZ

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

[Jeremy C. R. <re...@re...>]

On Fri, 1 Jun 2012, Jeremy C. Reed wrote:

> Our only problem noticed on MacOS X only is the ^@ null characters 

I was wrong about this. It is not MacOS specific. Looking at my ticket I 
see I forgot that this was also seen on my NetBSD production system.

> 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.)

Re: [Log4cplus-devel] request for feedback

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

On 1 June 2012 15:21, Jeremy C. Reed wrote:
> The BIND 10 team discussed this some. We posted some feedback at
> https://lists.isc.org/pipermail/bind10-dev/2012-May/003470.html and
> https://lists.isc.org/pipermail/bind10-dev/2012-May/003473.html
> I will repost that same feedback here:
>
>[...]
>
>  From: JINMEI Tatuya / ????
>
>> > 3. What do you miss in log4cplus?
>
> IIRC, log4cplus dumps its own warning messages to stdout or stderr,
> and they leak in an awkward way.  It would be nice if the application
> can control whether/how these messages are dumped.
There is a quiet mode that can be set using
log4cplus::helpers::LogLog::getLogLog()->setQuietMode(true). If it
still prints anything after this, it is probably a bug in log4cplus.
This is for 1.0.4.1. The syntax will be slightly different for trunk
and 1.1.x branches.

-- 
VZ

Re: [Log4cplus-devel] Unicode Text Logging

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

On 31 May 2012 19:21, Václav Zeman wrote:
> On 05/31/2012 05:46 PM, vvv jjj wrote:
>> Hi log4cplus Devel Team,
>>
>> Thanks Václav Zeman.
>>
>> I gave Unicode text directly in the cpp file. (Ex: CString str =
>> _T("Ω⅓∂₤◊");)
>> The file is saved with unicode support (the default yes button when
>> Unicode file is saved in Visual Studio 2008). The configuration used
>> is Debug Unicode dynamic library.
>>[...]
I have reproduced your problem on Windows as well. The problem is
Windows problem with its code pages.

Even though you are using the Debug_Unicode (or Release_Unicode)
configuration, which means that the output stream is std::wfstream,
the output file is always using chars (not wchar_ts). If you insist on
logging characters outside of your Windows code page, then you are
unfortunately (nearly) out of luck for 1.0.4.1.

The best way to work around this for 1.0.4.1 would be to derive your
own appender from *FileAppender that you use and either (1) override
its append() member function to do, either wchar_t -> UTF-8 (or any
other translation) on the fly, or, if you can use Visual Studio 2010,
(2) imbue the underlying file stream with, e.g.,
std::codecvt_utf8<tchar, 0x10FFFF,
static_cast<std::codecvt_mode>(std::consume_header |
std::little_endian)> facet.

For trunk and 1.1.x branches you can do (2) using imbue() member
function on *FileAppender.

-- 
VZ

Re: [Log4cplus-devel] request for feedback

[Jeremy C. R. <re...@re...>]

The BIND 10 team discussed this some. We posted some feedback at 
https://lists.isc.org/pipermail/bind10-dev/2012-May/003470.html and
https://lists.isc.org/pipermail/bind10-dev/2012-May/003473.html
I will repost that same feedback here:

 From: Shane Kerr 

> 1. What version of log4cplus are you using in what product/library of
> your own?

We work with 1.0.4 certainly. It was already out when we started using
log4cplus, so I don't know about support for earlier versions.
 
> 2. What lead you to choose log4cplus over other competing (log4cpp,
> log4cxx, Pantheios, etc.) libraries?

We always have license concerns (has to be BSD-compatible, so GPL code
is out) limiting our options. We had problems with incompatible APIs in
versions of log4cxx (IIRC), so we switched to log4cplus.

> 3. What do you miss in log4cplus?

Our main problems have to do with concurrent logging from multiple
processes. 

If log4cplus used only a single write() statement, and O_APPEND, when
writing to files then we would not have problems with files. We would
still have issues when writing to the console or other slow devices
(serial ports, etc.) since there is no guarantee that you will get your
entire buffer output.

To work around this in a general way we use advisory locks via fcntl()
to prevent concurrent logging. This seems to be the best solution, and
it would be nice to have this capability in log4cplus itself.

> 4. More comments?

We've found people who helped us get log4cplus into Debian and Ubuntu,
as well as some BSD variants. We'll be trying Fedora (and hopefully
RHEL) next. I'm happy if the log4cplus team wants to take up this
effort. :)

And thanks!

 From: JINMEI Tatuya / ????

> > 3. What do you miss in log4cplus?

IIRC, log4cplus dumps its own warning messages to stdout or stderr,
and they leak in an awkward way.  It would be nice if the application
can control whether/how these messages are dumped.

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

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

[Jeremy C. R. <re...@re...>]

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?

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.)

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

[Log4cplus-devel] MacOS X champion for log4cplus

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

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.

-- 
VZ

[Log4cplus-devel] [ log4cplus-Bugs-3531249 ] testing...

[SourceForge.net <no...@so...>]

Bugs item #3531249, was opened at 2012-05-31 22:27
Message generated for change (Settings changed) made by wilx
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=429073&aid=3531249&group_id=40830

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: Other
Group: None
>Status: Deleted
Resolution: None
Priority: 1
>Private: Yes
Submitted By: Václav Zeman (wilx)
Assigned to: Václav Zeman (wilx)
Summary: testing...

Initial Comment:
testing...

----------------------------------------------------------------------

Comment By: Václav Zeman (wilx)
Date: 2012-06-01 03:34

Message:
third test

----------------------------------------------------------------------

Comment By: Václav Zeman (wilx)
Date: 2012-06-01 03:24

Message:
testing....123

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=429073&aid=3531249&group_id=40830

[Log4cplus-devel] [ log4cplus-Bugs-3531249 ] testing...

[SourceForge.net <no...@so...>]

Bugs item #3531249, was opened at 2012-05-31 22:27
Message generated for change (Comment added) made by wilx
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=429073&aid=3531249&group_id=40830

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: Other
Group: None
Status: Open
Resolution: None
Priority: 1
Private: No
Submitted By: Václav Zeman (wilx)
Assigned to: Václav Zeman (wilx)
Summary: testing...

Initial Comment:
testing...

----------------------------------------------------------------------

>Comment By: Václav Zeman (wilx)
Date: 2012-06-01 03:34

Message:
third test

----------------------------------------------------------------------

Comment By: Václav Zeman (wilx)
Date: 2012-06-01 03:24

Message:
testing....123

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=429073&aid=3531249&group_id=40830

Re: [Log4cplus-devel] Unicode Text Logging

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

On 05/31/2012 05:46 PM, vvv jjj wrote:
> Hi log4cplus Devel Team,
>
> Thanks Václav Zeman.
>
> I gave Unicode text directly in the cpp file. (Ex: CString str =
> _T("Ω⅓∂₤◊");)
> The file is saved with unicode support (the default yes button when
> Unicode file is saved in Visual Studio 2008). The configuration used
> is Debug Unicode dynamic library.
>
> Please let me know if you need any other details.
>
> Regards
> J.Viswanath
>
> ------------------------------------------------------------------------
> *From:* Václav Zeman <vha...@gm...>
> *To:* vvv jjj <vv...@ya...>
> *Cc:* "log...@li..."
> <log...@li...>
> *Sent:* Thursday, 31 May 2012 3:11 PM
> *Subject:* Re: [Log4cplus-devel] Unicode Text Logging
>
> On 30 May 2012 19:08, vvv jjj wrote:
> > Hi log4cplus Devel Team,
> >
> > I got some bug when trying to log Unicode text. The logger could log
> ASCII
> > text correctly but when I give Unicode text the Logger is not
> logging any
> > other text also.
> >
> > Is this the same problem as Not able to log unicode character on Linux
> > Platform. - ID: 3446131.
> >
> > I'm using log4cplus in Windows XP with Visual Studio 2008. Working with
> > dynamic library with Debug Unicode support.
> >
> > Please let me know if it is the same problem and still existing.
> Also let me
> > know if there any option to support Unicode text logging without
> changing
> > the log4cplus library (1.0.4.1-RC2).
> How are you giving Unicode text to log4cplus? Is it part of your C++
> source? Then how is your C++ source encoded? What configuration of
> log4cplus are you using (Release or Release_Unicode)?
>
> -- 
> VZ
>
>
I have commented on the bug #3446131. But because your problems are on
Windows and not Linux, the solution might be different:

Ok, I think I have reproduced your problem with log4cplus 1.0.4.1
release.

The problem has two layers:

1. There is the std::locale::global (LOCALE); line that is or is not
   in your source, where LOCALE is either std::locale ("") or
   std::locale ().

2. ./configure script flags: NONE, --with-working-locale (and
   --with-working-c-locale or --with-iconv)

This gives us 6 combinations of these two parameters. To test this I
have used ftests/fileappender_test with "Entering loop číslo/番："
string to log. Log4cplus was compiled with CPPFLAGS="-DUNICODE=1".


(1)
no parameters to ./configure
std::locale::global: missing

The test breaks exactly as you have reported:

log4cplus: Just opened file: Test.log
log4cplus:WARN RollingFileAppender: MaxFileSize property value is too
small. Resetting to 204800.
log4cplus:ERROR file is not open: Test.log
log4cplus: Destroying appender named [First].
log4cplus: Destroying appender named [First].


(2)
no parameters to ./configure
std::locale::global(std::locale());

Same result as for (1).


(3)
no parameters to ./configure
std::locale::global(std::locale(""));

The logger keeps on logging. ASCII text goes through unmodified,
numbers get formatted according to my locale (my environment variable
LANG is set to en_US.UTF-8). The testing Unicode characters pass
through unmodified as well. I see 4 bytes per character
(sizeof(wchar_t) == 4 on Linux platforms).


(4)
std::locale::global: missing
./configure with --with-working-locale

The logging works but the non-ASCII characters are replaced by
question marks:

600 [139678217910080] DEBUG test.subtest <loop> - Entering loop
????slo/??????19759


(5)
std::locale::global(std::locale());
./configure with --with-working-locale

Same result as for (4).


(6)
std::locale::global(std::locale(""));
./configure with --with-working-locale

The logging works, numbers are formatted according to locale
(en_US.UTF-8) and the non-ASCII characters show up as well:

165 [139,711,023,560,512] DEBUG test.subtest <loop> - Entering loop
číslo/番：18,467


CONCLUSION

The whole matter is unfortunately very complicated. The result depends
on your locale settings, on capabilities of your compiler and standard
C++ library. It also depends on compile time settings of log4cplus
itself.

Unless you really (really) have to handle wchar_t strings, then I
strongly suggest that you do not compile log4cplus with -DUNICODE
switch. Most of Linux distributions these days use UTF-8 as their
native encoding and that passes through to the Test.log file unharmed
in all cases (that I have tested) whether the --with-working-locale
switch is present or not, whether any std::locale::global (LOCALE)
line is present or not.

Conclusion of the conclusion, I suggest configuring log4cplus on
_Linux_ platforms with GCC with the --with-working-locale switch and
_without_ -DUNICODE.

-- 
VZ

Re: [Log4cplus-devel] Unicode Text Logging

[vvv j. <vv...@ya...>]

Hi log4cplus Devel Team,

Thanks Václav Zeman. 


I gave Unicode text directly in the cpp file. (Ex: CString str = _T("Ω⅓∂₤◊");)
The file is saved with unicode support (the default yes button when Unicode file is saved in Visual Studio 2008). The configuration used is Debug Unicode dynamic library.

Please let me know if you need any other details.

Regards
J.Viswanath



________________________________
 From: Václav Zeman <vha...@gm...>
To: vvv jjj <vv...@ya...> 
Cc: "log...@li..." <log...@li...> 
Sent: Thursday, 31 May 2012 3:11 PM
Subject: Re: [Log4cplus-devel] Unicode Text Logging
 
On 30 May 2012 19:08, vvv jjj wrote:
> Hi log4cplus Devel Team,
>
> I got some bug when trying to log Unicode text. The logger could log ASCII
> text correctly but when I give Unicode text the Logger is not logging any
> other text also.
>
> Is this the same problem as Not able to log unicode character on Linux
> Platform. - ID: 3446131.
>
> I'm using log4cplus in Windows XP with Visual Studio 2008. Working with
> dynamic library with Debug Unicode support.
>
> Please let me know if it is the same problem and still existing. Also let me
> know if there any option to support Unicode text logging without changing
> the log4cplus library (1.0.4.1-RC2).
How are you giving Unicode text to log4cplus? Is it part of your C++
source? Then how is your C++ source encoded? What configuration of
log4cplus are you using (Release or Release_Unicode)?

-- 
VZ

Re: [Log4cplus-devel] Unicode Text Logging

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

On 30 May 2012 19:08, vvv jjj wrote:
> Hi log4cplus Devel Team,
>
> I got some bug when trying to log Unicode text. The logger could log ASCII
> text correctly but when I give Unicode text the Logger is not logging any
> other text also.
>
> Is this the same problem as Not able to log unicode character on Linux
> Platform. - ID: 3446131.
>
> I'm using log4cplus in Windows XP with Visual Studio 2008. Working with
> dynamic library with Debug Unicode support.
>
> Please let me know if it is the same problem and still existing. Also let me
> know if there any option to support Unicode text logging without changing
> the log4cplus library (1.0.4.1-RC2).
How are you giving Unicode text to log4cplus? Is it part of your C++
source? Then how is your C++ source encoded? What configuration of
log4cplus are you using (Release or Release_Unicode)?

-- 
VZ

[Log4cplus-devel] Unicode Text Logging

[vvv j. <vv...@ya...>]

Hi log4cplus Devel Team,

I got some bug when trying to log Unicode text. The logger could log ASCII text correctly but when I give Unicode text the Logger is not logging any other text also. 


Is this the same problem as Not able to log unicode character on Linux Platform. - ID: 3446131.

I'm using log4cplus in Windows XP with Visual Studio 2008. Working with dynamic library with Debug Unicode support. 


Please let me know if it is the same problem and still existing. Also let me know if there any option to support Unicode text logging without changing the log4cplus library (1.0.4.1-RC2). 


Thanks
J.Viswanath

Re: [Log4cplus-devel] DailyRollingFileAppender crashes with Ctrl-C

[vvv j. <vv...@ya...>]

Hi Václav Zeman

Thanks.

I got similar error as the Program crash on exit with the DailyRollingFileAppender - ID: 3471329. The callstack is also same. Regret for not providing the same callstack as I have problem with the machine.
The call stack is
tostring_internal(std::basic_string<char,std::char_traits<char>,std::allocator<char> > & outstr="", const wchar_t * src=0x017fa110, unsigned int size=31, std::locale loc={...}) Line 225 + 0x30 bytes C++
log4cplus::helpers::tostring(const std::basic_string<wchar_t,std::char_traits<wchar_t>,std::allocator<wchar_t> > & src="c:/temp/Eve/transaction.680.log", std::locale loc={...}) Line 264 + 0x65 bytes C++
log4cplus::FileAppender::open(int mode=18) Line 352 + 0x3c bytes C++
log4cplus::DailyRollingFileAppender::rollover() Line 709 C++
log4cplus::DailyRollingFileAppender::close() Line 635 C++
log4cplus::spi::LoggerImpl::closeNestedAppenders() Line 85 + 0x2a bytes C++
log4cplus::Logger::closeNestedAppenders() Line 215 + 0x17 bytes C++
log4cplus::Hierarchy::shutdown() Line 238 C++
log4cplus::Hierarchy::~Hierarchy() Line 80 C++
`log4cplus::Logger::getDefaultHierarchy'::`2'::`dynamic atexit destructor for 'defaultHierarchy''() + 0x28 bytes C++

Please let me know if I need to provide the exact call stack or if the bug cannot be reproduced with simple testcase when using DailyRollingFileAppender object.

Thanks and Regards
J.Viswanath



________________________________
 From: Václav Zeman <vha...@gm...>
To: vvv jjj <vv...@ya...> 
Cc: "log...@li..." <log...@li...> 
Sent: Wednesday, 30 May 2012 12:49 AM
Subject: Re: [Log4cplus-devel] DailyRollingFileAppender crashes with Ctrl-C
 
On 29 May 2012 18:17, vvv jjj wrote:
> Hi Václav Zeman
>
> Thanks for the quick response.
>
> The static linking issue which I mentioned is the one for the bug below
> Program crash on exit with the DailyRollingFileAppender - ID: 3471329
> I was asking if the bug is the same one which is causing the crash in my
> program.
If you are using static C and C++ run time libraries then it could be
the same reason. Unfortunately, linking statically to C and C++ run
time libraries cannot be supported. As the bug says, it is unsolvable
then. Use log4cplus with C and C++ DLL run time libraries.

>
> Regarding reproducing the bug, the tests does not directly produce the bug.
> But it can be easily produced by updating fileappender test with
> FileAppender changed to DailyRollingFileAppender.
>
> As per my understanding the problem is occurring when the application is
> exiting without calling Logger::Shutdown. I observed that the problem was
> occurring when I'm stopping the application with Control C, Logger::Shutdown
> is not invoked and some Rollback close is causing the crash.
>
> Please let me know if there is anything wrong with my understand. Also let
> me know is it valid to exit the application without calling Logger::Shutdown
> when using DailyRollingFileAppender.
Please try to reproduce the bug under Visual Studio debugger and
provide me with call stacks of all threads.

>> application is showing memory corruption message box.When I disable the
>> support of DailyRollingFileAppender it is working fine. I think that there
>> is some memory corruption when using DailyRollingFileAppender in
>> application
>> which is closed using Ctrl-C.
>>
>> The details of log4cplus are:
>> log4cplus:
>>     1.0.4.1-RC2 version
>>     build system that you are building log4cplus with Visual Studio
>> solution
>>     Visual Studio – project configuration (Debug_Unicode)
>>     target OS Windows XP and CPU Intel
>>
>> log4cplus client application:
>>     shared library log4cplus
>>     library file you are linking your application with –
>> log4cplusUSD.lib,
>> liblog4cplus.dll.a, etc., on Windows
>>     your application is using Unicode/wchar_t
>>
>> Also I have seen that DailyRollingFileAppender has some issue with static
>> linking. Is that issue fixed or is it related to the problem which I'm
>> facing?
> I have not seen any issues with static linking. What problems do you see?
>
>>
>> Please let me know if anything is not clear or need any other details.
>>
>> Thanks and Regards
>> J.Viswanath
> Thank you for the problem report. Is this reproducible with any of the
> tests in tests/ directory? If not, could you provide a self contained
> test case?

-- 
VZ

Re: [Log4cplus-devel] DailyRollingFileAppender crashes with Ctrl-C

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

On 29 May 2012 18:17, vvv jjj wrote:
> Hi Václav Zeman
>
> Thanks for the quick response.
>
> The static linking issue which I mentioned is the one for the bug below
> Program crash on exit with the DailyRollingFileAppender - ID: 3471329
> I was asking if the bug is the same one which is causing the crash in my
> program.
If you are using static C and C++ run time libraries then it could be
the same reason. Unfortunately, linking statically to C and C++ run
time libraries cannot be supported. As the bug says, it is unsolvable
then. Use log4cplus with C and C++ DLL run time libraries.

>
> Regarding reproducing the bug, the tests does not directly produce the bug.
> But it can be easily produced by updating fileappender test with
> FileAppender changed to DailyRollingFileAppender.
>
> As per my understanding the problem is occurring when the application is
> exiting without calling Logger::Shutdown. I observed that the problem was
> occurring when I'm stopping the application with Control C, Logger::Shutdown
> is not invoked and some Rollback close is causing the crash.
>
> Please let me know if there is anything wrong with my understand. Also let
> me know is it valid to exit the application without calling Logger::Shutdown
> when using DailyRollingFileAppender.
Please try to reproduce the bug under Visual Studio debugger and
provide me with call stacks of all threads.

>> application is showing memory corruption message box.When I disable the
>> support of DailyRollingFileAppender it is working fine. I think that there
>> is some memory corruption when using DailyRollingFileAppender in
>> application
>> which is closed using Ctrl-C.
>>
>> The details of log4cplus are:
>> log4cplus:
>>     1.0.4.1-RC2 version
>>     build system that you are building log4cplus with Visual Studio
>> solution
>>     Visual Studio – project configuration (Debug_Unicode)
>>     target OS Windows XP and CPU Intel
>>
>> log4cplus client application:
>>     shared library log4cplus
>>     library file you are linking your application with –
>> log4cplusUSD.lib,
>> liblog4cplus.dll.a, etc., on Windows
>>     your application is using Unicode/wchar_t
>>
>> Also I have seen that DailyRollingFileAppender has some issue with static
>> linking. Is that issue fixed or is it related to the problem which I'm
>> facing?
> I have not seen any issues with static linking. What problems do you see?
>
>>
>> Please let me know if anything is not clear or need any other details.
>>
>> Thanks and Regards
>> J.Viswanath
> Thank you for the problem report. Is this reproducible with any of the
> tests in tests/ directory? If not, could you provide a self contained
> test case?

-- 
VZ

Re: [Log4cplus-devel] DailyRollingFileAppender crashes with Ctrl-C

[vvv j. <vv...@ya...>]

Hi Václav Zeman

Thanks for the quick response. 


The static linking issue which I mentioned is the one for the bug below
Program crash on exit with the DailyRollingFileAppender - ID: 3471329
I was asking if the bug is the same one which is causing the crash in my program.

Regarding reproducing the bug, the tests does not directly produce the bug. But it can be easily produced by updating fileappender test with FileAppender changed to DailyRollingFileAppender.

As per my understanding the problem is occurring when the application is exiting without calling Logger::Shutdown. I observed that the problem was occurring when I'm stopping the application with Control C, Logger::Shutdown is not invoked and some Rollback close is causing the crash.

Please let me know if there is anything wrong with my understand. Also let me know is it valid to exit the application without calling Logger::Shutdown when using DailyRollingFileAppender.

Thanks and Regards
J.Viswanath


________________________________
 From: Václav Zeman <vha...@gm...>
To: vvv jjj <vv...@ya...> 
Cc: "log...@li..." <log...@li...> 
Sent: Tuesday, 29 May 2012 2:16 PM
Subject: Re: [Log4cplus-devel] DailyRollingFileAppender crashes with Ctrl-C
 
On 29 May 2012 05:20, vvv jjj wrote:
> Hi log4cplus Devel Team,
>
> This is my first mail to this form about log4cplus bug. Please let me know
> if I posted in the wrong form.
>
>  I'm using log4plus for logging in my application which is working fine.
> When using DailyRollingFileAppender it is working fine when my application
> is running completely. But when I stop my application with Ctrl-C, then my
> application is showing memory corruption message box.When I disable the
> support of DailyRollingFileAppender it is working fine. I think that there
> is some memory corruption when using DailyRollingFileAppender in application
> which is closed using Ctrl-C.
>
> The details of log4cplus are:
> log4cplus:
>     1.0.4.1-RC2 version
>     build system that you are building log4cplus with Visual Studio solution
>     Visual Studio – project configuration (Debug_Unicode)
>     target OS Windows XP and CPU Intel
>
> log4cplus client application:
>     shared library log4cplus
>     library file you are linking your application with –  log4cplusUSD.lib,
> liblog4cplus.dll.a, etc., on Windows
>     your application is using Unicode/wchar_t
>
> Also I have seen that DailyRollingFileAppender has some issue with static
> linking. Is that issue fixed or is it related to the problem which I'm
> facing?
I have not seen any issues with static linking. What problems do you see?

>
> Please let me know if anything is not clear or need any other details.
>
> Thanks and Regards
> J.Viswanath
Thank you for the problem report. Is this reproducible with any of the
tests in tests/ directory? If not, could you provide a self contained
test case?

-- 
VZ

Re: [Log4cplus-devel] DailyRollingFileAppender crashes with Ctrl-C

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

On 29 May 2012 05:20, vvv jjj wrote:
> Hi log4cplus Devel Team,
>
> This is my first mail to this form about log4cplus bug. Please let me know
> if I posted in the wrong form.
>
>  I'm using log4plus for logging in my application which is working fine.
> When using DailyRollingFileAppender it is working fine when my application
> is running completely. But when I stop my application with Ctrl-C, then my
> application is showing memory corruption message box.When I disable the
> support of DailyRollingFileAppender it is working fine. I think that there
> is some memory corruption when using DailyRollingFileAppender in application
> which is closed using Ctrl-C.
>
> The details of log4cplus are:
> log4cplus:
>     1.0.4.1-RC2 version
>     build system that you are building log4cplus with Visual Studio solution
>     Visual Studio – project configuration (Debug_Unicode)
>     target OS Windows XP and CPU Intel
>
> log4cplus client application:
>     shared library log4cplus
>     library file you are linking your application with –  log4cplusUSD.lib,
> liblog4cplus.dll.a, etc., on Windows
>     your application is using Unicode/wchar_t
>
> Also I have seen that DailyRollingFileAppender has some issue with static
> linking. Is that issue fixed or is it related to the problem which I'm
> facing?
I have not seen any issues with static linking. What problems do you see?

>
> Please let me know if anything is not clear or need any other details.
>
> Thanks and Regards
> J.Viswanath
Thank you for the problem report. Is this reproducible with any of the
tests in tests/ directory? If not, could you provide a self contained
test case?

-- 
VZ

[Log4cplus-devel] DailyRollingFileAppender crashes with Ctrl-C

[vvv j. <vv...@ya...>]

Hi log4cplus Devel Team,

This is my first mail to this form about log4cplus bug. Please let me know if I posted in the wrong form.

 I'm
 using log4plus for logging in my application which is working fine. 
When using DailyRollingFileAppender it is working fine when my 
application is running completely. But when I stop my application with 
Ctrl-C, then my application is showing memory corruption message 
box.When I disable the support of DailyRollingFileAppender it is working
 fine. I think that there is some memory corruption when using 
DailyRollingFileAppender in application which is closed using Ctrl-C.

The details of log4cplus
 are:
log4cplus:
    1.0.4.1-RC2 version
    build system that you are building log4cplus with Visual Studio solution
    Visual Studio – project configuration (Debug_Unicode)
    target OS Windows XP and CPU Intel

log4cplus client application:
    shared library log4cplus
    library file you are linking your application with –  log4cplusUSD.lib, liblog4cplus.dll.a, etc., on Windows
    your application is using Unicode/wchar_t 

Also
 I have seen that DailyRollingFileAppender has some issue with static 
linking. Is that issue fixed or is it related to the problem which I'm 
facing?

Please let me know if anything is not clear or need any other details.

Thanks and Regards
J.Viswanath

[Log4cplus-devel] log4cplus 1.0.4.1 released

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

Hi.

I have released log4cplus 1.0.4.1. There are no significant changes
compared to 1.0.4.1-RC2. This is a bug fix release. This is likely the last
release from 1.0.x code base. Further releases will be based on trunk
and 1.1.x branches.


Version 1.0.4.1

  - There are no significant changes compared to 1.0.4.1-RC2.

Version 1.0.4.1-RC2

  - Fixed bug #3520891 - FileAppender buffer size override does not
    work.
  - Update to Autoconf 2.69, Automake 1.12 and Libtool 2.4.2.
  - Improved Solaris Studio support.
  - Fixed detection of clock_gettime() on Linux.

Version 1.0.4.1-RC1

  - Fixed use of uninitialized member in ConfigurationWatchDogThread.
  - Updated libtool to 2.4; updated configure macros.
  - Improved resource and error handling in NTEventLogAppender and
    Win32 sockets code.
  - Limit the logged text size to 31839 for NTEventLogAppender as per
    MSDN recommendation.
  - Use range checks instead of equality checks when converting
    LogLevel value to NT EventLog category and event type to allow
    user defined log levels to work.
  - Fixed issue with function-try-catch blocks in dtors.


-- 
VZ

Re: [Log4cplus-devel] request for feedback

[Alexander N. <neu...@kd...>]

On Wednesday 16 May 2012, Václav Zeman wrote:
> Hi.
> 
> I have only recently realized that log4cplus is being used wider than
> I thought. The most important (in my eyes) piece of software that I
> have recently discovered using log4cplus is BIND 10. This led me to
> realization that I need more information about log4cplus' users and
> uses. Thus I would like to ask you for feedback about log4cplus. Feel
> free to post answers to following questions to
> <log...@li...> mailing list or privately to
> myself.
> 
> 1. What version of log4cplus are you using in what product/library of your
> own?
> 
> 2. What lead you to choose log4cplus over other competing (log4cpp,
> log4cxx, Pantheios, etc.) libraries?

It is relatively small.
It is "alive".
It has a license which allows it to be used in proprietary applications.
It doesn't have any extra dependencies.

> 3. What do you miss in log4cplus?

I'm using the Rolling File Appender, and use the day of the week as part of 
the filename, so there are in general log files from the last 7 days present. 
Now it would be nice if it would also start a new log file at midnight.
As it is now, if the log file is started Monday and the application runs for 
more days, all logging still goes into the same file (as long as the maximum 
size has not been reached).

> 4. More comments?

Works great :-)

Alex

[Log4cplus-devel] request for feedback

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

Hi.

I have only recently realized that log4cplus is being used wider than
I thought. The most important (in my eyes) piece of software that I
have recently discovered using log4cplus is BIND 10. This led me to
realization that I need more information about log4cplus' users and
uses. Thus I would like to ask you for feedback about log4cplus. Feel
free to post answers to following questions to
<log...@li...> mailing list or privately to
myself.

1. What version of log4cplus are you using in what product/library of your own?

2. What lead you to choose log4cplus over other competing (log4cpp,
log4cxx, Pantheios, etc.) libraries?

3. What do you miss in log4cplus?

4. More comments?

-- 
VZ

[Log4cplus-devel] log4cplus 1.0.4.1-RC2 released

[Václav Z. <v.h...@sh...>]

Hi.

I have released log4cplus 1.0.4.1-RC2. There is only a handful of
improvements in the release:

  - Fixed bug #3520891 - FileAppender buffer size override does not
    work.
  - Update to Autoconf 2.69, Automake 1.12 and Libtool 2.4.2.
  - Improved Solaris Studio support.
  - Fixed detection of clock_gettime() on Linux.

-- 
VZ

[Log4cplus-devel] log4cplus 1.1.0-RC5 released

[Václav Z. <v.h...@sh...>]

Hi.

I have released log4cplus 1.1.0-RC5. There are only some minor bug fixes
and additions:

- Fixed single threaded log4cplus build issues.

- Added ability to log to std::cerr (Andreas Bießmann).

- Fixed disabling of LOG4CPLUS_*_FMT() macros.


-- 
VZ

Re: [Log4cplus-devel] "Hello World" example needs to be updated?

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

On 05/09/2012 04:03 PM, A Richardson wrote:
> I just got started with log4cplus, and noticed compile errors in the
> example at:
>
> http://log4cplus.sourceforge.net/hello_world.html
>
> I am using log4cplus 1.1.0rc4. Compiling the example complains about
> LOG4CPLUS_WARN not existing. Replacing the #include on logger.h with
> #include <log4cplus/loggingmacros.h> seems to resolve the issue.
Thank you for the problem report. I have updated the examples on the site.

-- 
VZ