log4cplus-devel Mailing List for log4cplus (Page 9)
Logging Framework for C++
Brought to you by:
wilx
Menu
▾
▴
log4cplus-devel — Mailing list for log4cplus developers
You can subscribe to this list here.
| 2003 |
Jan
|
Feb
|
Mar
(2) |
Apr
(2) |
May
(1) |
Jun
|
Jul
|
Aug
(2) |
Sep
(3) |
Oct
|
Nov
|
Dec
|
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2004 |
Jan
|
Feb
(1) |
Mar
|
Apr
|
May
(1) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2005 |
Jan
|
Feb
(1) |
Mar
|
Apr
(1) |
May
|
Jun
|
Jul
|
Aug
(1) |
Sep
|
Oct
|
Nov
|
Dec
(1) |
| 2006 |
Jan
|
Feb
(1) |
Mar
|
Apr
(1) |
May
(1) |
Jun
|
Jul
|
Aug
(1) |
Sep
|
Oct
(3) |
Nov
(7) |
Dec
(15) |
| 2007 |
Jan
(19) |
Feb
(23) |
Mar
(40) |
Apr
(36) |
May
(18) |
Jun
(8) |
Jul
(10) |
Aug
(18) |
Sep
(18) |
Oct
(4) |
Nov
(1) |
Dec
(4) |
| 2008 |
Jan
(2) |
Feb
(1) |
Mar
(4) |
Apr
(16) |
May
(17) |
Jun
(15) |
Jul
(23) |
Aug
(7) |
Sep
(2) |
Oct
|
Nov
|
Dec
|
| 2009 |
Jan
(2) |
Feb
(1) |
Mar
(1) |
Apr
(7) |
May
|
Jun
(5) |
Jul
(2) |
Aug
(9) |
Sep
|
Oct
(4) |
Nov
(6) |
Dec
(4) |
| 2010 |
Jan
(2) |
Feb
(2) |
Mar
(6) |
Apr
(5) |
May
(2) |
Jun
(13) |
Jul
(5) |
Aug
|
Sep
(2) |
Oct
(2) |
Nov
|
Dec
|
| 2011 |
Jan
(1) |
Feb
|
Mar
|
Apr
(2) |
May
(2) |
Jun
(11) |
Jul
(1) |
Aug
(4) |
Sep
(5) |
Oct
|
Nov
(4) |
Dec
|
| 2012 |
Jan
|
Feb
(13) |
Mar
(3) |
Apr
(5) |
May
(18) |
Jun
(22) |
Jul
(11) |
Aug
(25) |
Sep
(56) |
Oct
(1) |
Nov
(28) |
Dec
(3) |
| 2013 |
Jan
(66) |
Feb
(40) |
Mar
(61) |
Apr
(1) |
May
(45) |
Jun
(30) |
Jul
(30) |
Aug
(46) |
Sep
(23) |
Oct
(43) |
Nov
(95) |
Dec
(27) |
| 2014 |
Jan
(16) |
Feb
(19) |
Mar
(23) |
Apr
(18) |
May
(22) |
Jun
(12) |
Jul
(15) |
Aug
(16) |
Sep
(30) |
Oct
(10) |
Nov
(10) |
Dec
(5) |
| 2015 |
Jan
(2) |
Feb
(7) |
Mar
|
Apr
(1) |
May
(10) |
Jun
(3) |
Jul
(1) |
Aug
(5) |
Sep
|
Oct
(6) |
Nov
(2) |
Dec
(15) |
| 2016 |
Jan
(21) |
Feb
(6) |
Mar
(30) |
Apr
(12) |
May
(11) |
Jun
(4) |
Jul
(2) |
Aug
(7) |
Sep
(13) |
Oct
|
Nov
(6) |
Dec
(8) |
| 2017 |
Jan
(21) |
Feb
(5) |
Mar
(7) |
Apr
(3) |
May
|
Jun
(4) |
Jul
(18) |
Aug
(1) |
Sep
|
Oct
|
Nov
|
Dec
|
| 2018 |
Jan
(1) |
Feb
|
Mar
(2) |
Apr
(1) |
May
(4) |
Jun
|
Jul
|
Aug
(1) |
Sep
|
Oct
|
Nov
|
Dec
(1) |
| 2019 |
Jan
|
Feb
|
Mar
(1) |
Apr
(1) |
May
|
Jun
|
Jul
(4) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(2) |
| 2020 |
Jan
|
Feb
|
Mar
|
Apr
(2) |
May
(1) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2021 |
Jan
|
Feb
(1) |
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
(1) |
Sep
|
Oct
|
Nov
|
Dec
|
| 2022 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
(1) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2023 |
Jan
|
Feb
(3) |
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(1) |
Dec
|
| 2024 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(2) |
Nov
|
Dec
|
|
From: Vladimir \Equidamoid\ S. <equ...@gm...> - 2013-08-12 17:13:48
|
Hello, I'm trying to build log4cplus for android using cmake (added 'add_subdirectory(path/to/the/source)' to my main CMakeLists.txt). The build crashes with the following error: [ 48%] Building CXX object jni/lib/log4cplus-1.1.1/src/CMakeFiles/log4cplus.dir/global-init.cxx.o jni/lib/log4cplus-1.1.1/src/global-init.cxx:268:46: error: log4cplus::internal::__emutls_t._ZN9log4cplus8internal3ptdE causes a section type conflict with log4cplus::internal::ptd jni/lib/log4cplus-1.1.1/src/global-init.cxx:268:46: note: 'log4cplus::internal::ptd' was declared here Is this a bug or I'm doing something wrong? Best regards, Vladimir |
|
From: Václav Z. <vha...@gm...> - 2013-07-15 21:54:14
|
Hi. As SourceForge is not going to support Bazaar anymore, I have decided to move log4cplus source code hosting from SourceForge to Launchpad.net (https://launchpad.net/log4cplus). I have decided to stick with Bazaar for some more time instead of moving to Github because it simply requires less effort than having to start using Git and Github. I am moving only the source code repository. Everything else (bug tracker, pages, etc.) stays on SourceForge. -- VZ |
|
From: Václav Z. <wi...@us...> - 2013-07-14 12:59:34
|
Tickets were moved from [log4cplus:support-requests] to [log4cplus:bugs] - log4cplus:support-requests:#4 --> log4cplus:bugs:#242 Static Link Error - log4cplus:support-requests:#11 --> log4cplus:bugs:#249 Difference between log4cplus.dsw and log4cplus_uni.dsw - log4cplus:support-requests:#3 --> log4cplus:bugs:#241 Link Error - log4cplus:support-requests:#23 --> log4cplus:bugs:#260 Help with creating a static library of log4cplus.a - log4cplus:support-requests:#18 --> log4cplus:bugs:#256 std::use_facet<CodeCvt>(loc) returs deleted object - log4cplus:support-requests:#31 --> log4cplus:bugs:#267 Set filter using properties file - log4cplus:support-requests:#33 --> log4cplus:bugs:#269 Compiling with C++11 support - log4cplus:support-requests:#27 --> log4cplus:bugs:#263 MDC - log4cplus:support-requests:#5 --> log4cplus:bugs:#243 Tracing destructors - log4cplus:support-requests:#9 --> log4cplus:bugs:#247 'Unresolved External' in thread_test with VC7 - log4cplus:support-requests:#2 --> log4cplus:bugs:#240 missing logs - loggingserver is slower than socket_test - log4cplus:support-requests:#8 --> log4cplus:bugs:#246 Windows console and blocking? - log4cplus:support-requests:#7 --> log4cplus:bugs:#245 lost vftables - log4cplus:support-requests:#29 --> log4cplus:bugs:#265 How to create NTEventlogAppender.dll as required for logging - log4cplus:support-requests:#16 --> log4cplus:bugs:#254 Compile errors when installing the Framework - log4cplus:support-requests:#35 --> log4cplus:bugs:#271 log4cplus and lnk2001 errors - log4cplus:support-requests:#13 --> log4cplus:bugs:#251 Log4cplus in a large project - log4cplus:support-requests:#28 --> log4cplus:bugs:#264 Change dynamically rollinglogfile name by thread - log4cplus:support-requests:#17 --> log4cplus:bugs:#255 configandwatch - log4cplus:support-requests:#32 --> log4cplus:bugs:#268 creating custom log level and setting it from prperty file - log4cplus:support-requests:#37 --> log4cplus:bugs:#272 Problem with macros_get_logger - log4cplus:support-requests:#15 --> log4cplus:bugs:#253 There are neither source nor inlcude files - log4cplus:support-requests:#6 --> log4cplus:bugs:#244 Program crashes when used in Purify - log4cplus:support-requests:#20 --> log4cplus:bugs:#258 chainsaw support - log4cplus:support-requests:#34 --> log4cplus:bugs:#270 Buffer overrun with Hello World example - log4cplus:support-requests:#25 --> log4cplus:bugs:#261 log4cplus::Logger thread safety - log4cplus:support-requests:#1 --> log4cplus:bugs:#239 Failing to link static library under MVC++ 6.0 - log4cplus:support-requests:#12 --> log4cplus:bugs:#250 Problems with 1.1.0 beta1 - log4cplus:support-requests:#26 --> log4cplus:bugs:#262 How do I reload properties while running? - log4cplus:support-requests:#19 --> log4cplus:bugs:#257 Date and time in log filename - log4cplus:support-requests:#21 --> log4cplus:bugs:#259 Deadlock after calling logDebug funtion - log4cplus:support-requests:#14 --> log4cplus:bugs:#252 There are neither source nor inlcude files - log4cplus:support-requests:#30 --> log4cplus:bugs:#266 Multiple Instances - log4cplus:support-requests:#10 --> log4cplus:bugs:#248 True UNICODE file/console output in Windows |
|
From: Václav Z. <wi...@us...> - 2013-07-14 12:58:31
|
Tickets were moved from [log4cplus:support-requests] to [log4cplus:bugs] - log4cplus:support-requests:#22 --> log4cplus:bugs:#235 Setting up logger from Properties fails (?) - log4cplus:support-requests:#38 --> log4cplus:bugs:#238 How to check if configuration has been run? - log4cplus:support-requests:#36 --> log4cplus:bugs:#237 Loggingmacros.h no longer included in logger.h - log4cplus:support-requests:#24 --> log4cplus:bugs:#236 Log output corruption on Windows 7 |
|
From: Václav Z. <wi...@us...> - 2013-07-14 12:58:26
|
Tickets were moved from [log4cplus:patches] to [log4cplus:bugs]
- log4cplus:patches:#3 --> log4cplus:bugs:#208 Pattern Layout: line not displayed
- log4cplus:patches:#24 --> log4cplus:bugs:#228 Patch for feature request 3034780
- log4cplus:patches:#6 --> log4cplus:bugs:#211 OutputDebugString
- log4cplus:patches:#29 --> log4cplus:bugs:#232 update for cmake build tool
- log4cplus:patches:#4 --> log4cplus:bugs:#209 Fix segmentation fault (gcc on Solaris)
- log4cplus:patches:#15 --> log4cplus:bugs:#219 Patch for REL_1_0_3-RC2 to compile with VC 8.0
- log4cplus:patches:#17 --> log4cplus:bugs:#221 Add hostname fields to PatternLayout
- log4cplus:patches:#31 --> log4cplus:bugs:#234 cmake // Detect version from version.h file
- log4cplus:patches:#27 --> log4cplus:bugs:#230 fix move ctor for DiagnosticContext
- log4cplus:patches:#20 --> log4cplus:bugs:#224 FileAppender log re-open after I/O failure
- log4cplus:patches:#5 --> log4cplus:bugs:#210 Fixed Single-Threaded Compilation
- log4cplus:patches:#21 --> log4cplus:bugs:#225 Correct delete in FileAppender
- log4cplus:patches:#23 --> log4cplus:bugs:#227 Infinite loop when hierarchy starts with a dot
- log4cplus:patches:#11 --> log4cplus:bugs:#216 Cygwin Patches
- log4cplus:patches:#13 --> log4cplus:bugs:#218 Bugfix for PatternLayout
- log4cplus:patches:#7 --> log4cplus:bugs:#212 Win32 debugger appender
- log4cplus:patches:#12 --> log4cplus:bugs:#217 Added API for passing in __FUNCTION__ similar to __FILE__
- log4cplus:patches:#2 --> log4cplus:bugs:#207 Configurable appender's threshold in property file
- log4cplus:patches:#8 --> log4cplus:bugs:#213 Fix 1.0.1 build on cygwin
- log4cplus:patches:#30 --> log4cplus:bugs:#233 Updates for cmake on 1.1.x branch
- log4cplus:patches:#22 --> log4cplus:bugs:#226 Infinite loop when '}' option marker is missing
- log4cplus:patches:#16 --> log4cplus:bugs:#220 REL_1_0_3-RC4 Unicode under Linux
- log4cplus:patches:#10 --> log4cplus:bugs:#215 fix for FreeBSD build of 1.0.2
- log4cplus:patches:#18 --> log4cplus:bugs:#222 Make log4cplus -Wshadow-clean
- log4cplus:patches:#25 --> log4cplus:bugs:#229 Code duplication in FileAppender's ::append()
- log4cplus:patches:#19 --> log4cplus:bugs:#223 Add %i to PatternLayout for the process ID
- log4cplus:patches:#1 --> log4cplus:bugs:#206 patch to avoid g++ warnings
- log4cplus:patches:#28 --> log4cplus:bugs:#231 android support for cmake build system
- log4cplus:patches:#9 --> log4cplus:bugs:#214 Recursive ${xyz} configuration variable replacement
|
|
From: Václav Z. <wi...@us...> - 2013-07-14 12:57:11
|
Tickets were moved from [log4cplus:patches] to [log4cplus:bugs] - log4cplus:patches:#14 --> log4cplus:bugs:#204 fileappender with 0 as maxBackupIndex - log4cplus:patches:#26 --> log4cplus:bugs:#205 Improved cmake support on Linux |
|
From: Václav Z. <wi...@us...> - 2013-07-14 12:56:27
|
Tickets were moved from [log4cplus:feature-requests] to [log4cplus:bugs] - log4cplus:feature-requests:#20 --> log4cplus:bugs:#198 Add read access to property filename - log4cplus:feature-requests:#5 --> log4cplus:bugs:#187 'Append' mode when using FileAppended from cfg file. - log4cplus:feature-requests:#13 --> log4cplus:bugs:#193 syslog appender with win32 system - log4cplus:feature-requests:#10 --> log4cplus:bugs:#191 True UNICODE file/console output in Windows - log4cplus:feature-requests:#24 --> log4cplus:bugs:#200 Print some kind of warning when maxFileSIze is too low - log4cplus:feature-requests:#22 --> log4cplus:bugs:#199 Function name for pattern layout - log4cplus:feature-requests:#19 --> log4cplus:bugs:#197 Add a native Win32 Console Appender - log4cplus:feature-requests:#25 --> log4cplus:bugs:#201 Add conversion pattern for basename of file - log4cplus:feature-requests:#11 --> log4cplus:bugs:#192 Stream suppport - log4cplus:feature-requests:#15 --> log4cplus:bugs:#194 Support Windows x64 platform - log4cplus:feature-requests:#18 --> log4cplus:bugs:#196 Crash on null pointer - log4cplus:feature-requests:#1 --> log4cplus:bugs:#184 Windows Event Log Appender - log4cplus:feature-requests:#28 --> log4cplus:bugs:#202 question about the '%F' layout pattern - log4cplus:feature-requests:#6 --> log4cplus:bugs:#188 NTEventLogAppender: configure local server source - log4cplus:feature-requests:#8 --> log4cplus:bugs:#190 cooperation with OpenC++? - log4cplus:feature-requests:#2 --> log4cplus:bugs:#185 need to derive from the Logger class - log4cplus:feature-requests:#7 --> log4cplus:bugs:#189 Pimpl idiom - log4cplus:feature-requests:#32 --> log4cplus:bugs:#203 Log time in micro/nano sections - log4cplus:feature-requests:#3 --> log4cplus:bugs:#186 Milli- and Micro-second time format - log4cplus:feature-requests:#17 --> log4cplus:bugs:#195 Add read access to properties |
|
From: Václav Z. <wi...@us...> - 2013-07-14 12:54:22
|
Tickets were moved from [log4cplus:feature-requests] to [log4cplus:bugs] - log4cplus:feature-requests:#31 --> log4cplus:bugs:#182 Check for changes to .properties file - log4cplus:feature-requests:#30 --> log4cplus:bugs:#179 SysLog over TCP - log4cplus:feature-requests:#29 --> log4cplus:bugs:#178 Persist Logging Levels |
|
From: Václav Z. <wi...@us...> - 2013-07-14 12:54:22
|
Tickets were moved from [log4cplus:feature-requests] to [log4cplus:bugs] - log4cplus:feature-requests:#16 --> log4cplus:bugs:#173 Error reporting for property files - log4cplus:feature-requests:#4 --> log4cplus:bugs:#169 Roll over time fpr DailyRollingFileAppender - log4cplus:feature-requests:#27 --> log4cplus:bugs:#177 a rolling-appenders question - log4cplus:feature-requests:#9 --> log4cplus:bugs:#170 add own conversionrules - log4cplus:feature-requests:#21 --> log4cplus:bugs:#174 Another naming rule for RollingFileappender - log4cplus:feature-requests:#29 --> log4cplus:bugs:#180 Persist Logging Levels - log4cplus:feature-requests:#30 --> log4cplus:bugs:#181 SysLog over TCP - log4cplus:feature-requests:#26 --> log4cplus:bugs:#176 Reading UTF-16 properties file - log4cplus:feature-requests:#31 --> log4cplus:bugs:#183 Check for changes to .properties file - log4cplus:feature-requests:#12 --> log4cplus:bugs:#171 Extend property files syntax/capabilities. - log4cplus:feature-requests:#14 --> log4cplus:bugs:#172 Add a XML configurator - log4cplus:feature-requests:#23 --> log4cplus:bugs:#175 Different pattern for different log levels |
|
From: Sergei N. <ser...@gm...> - 2013-07-08 15:35:19
|
Hi,
Is it possible to configure FileAppender with filename constructed during
initialization?
For example - can log4cplus understand following construction?
log4cplus.appender.FA=log4cplus::RollingFileAppender
log4cplus.appender.FA.File = ${appname}_${pid}.log
Where ${appname} and ${pid} - predefined macro for properties file as in
log4j.
Thank you.
--
Best Regards,
Sergei Nikulov
|
|
From: Sergei N. <ser...@gm...> - 2013-07-06 14:55:41
|
2013/7/6 Václav Zeman <vha...@gm...> > So it has happened that I have received responses to two of my tickets > filled in against SourceForge itself. The responses boil down to that > SourceForge is no longer able to support Bazaar. They have stopped > offering Bazaar for new projects. > > So, now I need to decide where am I going to move log4cplus sources to. > As far as I can see, the axis of this decision are: > > 1. stay on SF or move to Github/Bitbutcket/Launchpad > +1 for Github (bugtracker, CI - https://travis-ci.org/) > 2. stay with Bazaar (and move anywhere where it will be supported) or > move to Git or Mercurial (I do not see a third DVCS option here. Is > there any such option that I am missing?) > > Opinions? > > -- > VZ > > > -- Best Regards, Sergei Nikulov |
|
From: Václav Z. <vha...@gm...> - 2013-07-06 10:34:07
|
On 07/04/2013 09:23 AM, Václav Zeman wrote: > On 07/04/2013 08:34 AM, Sergei Nikulov wrote: >> >> 2013/7/4 Václav Zeman <vha...@gm... <mailto:vha...@gm...>> >> >> Hi. >> >> Per popular request, I have set up a mirror of log4cplus trunk on >> Github: <https://github.com/wilx/log4cplus-trunk> >> >> The mirror is updated hourly by a cron job on my box, so it should be >> fairly up to date. At this point, the mirror is one way only, from >> SourceForge to Github. >> >> >> Hi Václav, >> >> Can we now submit pull requests through github? > I want to keep the master on Github to be unmodified mirror of the > Bazaar trunk branch. I guess, for this to work, I would have to create > another branch and pull into that branch instead and then sync with > Bazaar repository, somehow. > > You could try to send me a pull request and I will try to figure out how > to do this. So it has happened that I have received responses to two of my tickets filled in against SourceForge itself. The responses boil down to that SourceForge is no longer able to support Bazaar. They have stopped offering Bazaar for new projects. So, now I need to decide where am I going to move log4cplus sources to. As far as I can see, the axis of this decision are: 1. stay on SF or move to Github/Bitbutcket/Launchpad 2. stay with Bazaar (and move anywhere where it will be supported) or move to Git or Mercurial (I do not see a third DVCS option here. Is there any such option that I am missing?) Opinions? -- VZ |
|
From: Václav Z. <vha...@gm...> - 2013-07-04 07:24:00
|
On 07/04/2013 08:34 AM, Sergei Nikulov wrote: > > 2013/7/4 Václav Zeman <vha...@gm... <mailto:vha...@gm...>> > > Hi. > > Per popular request, I have set up a mirror of log4cplus trunk on > Github: <https://github.com/wilx/log4cplus-trunk> > > The mirror is updated hourly by a cron job on my box, so it should be > fairly up to date. At this point, the mirror is one way only, from > SourceForge to Github. > > > Hi Václav, > > Can we now submit pull requests through github? I want to keep the master on Github to be unmodified mirror of the Bazaar trunk branch. I guess, for this to work, I would have to create another branch and pull into that branch instead and then sync with Bazaar repository, somehow. You could try to send me a pull request and I will try to figure out how to do this. -- VZ |
|
From: Sergei N. <ser...@gm...> - 2013-07-04 06:35:02
|
2013/7/4 Václav Zeman <vha...@gm...> > Hi. > > Per popular request, I have set up a mirror of log4cplus trunk on > Github: <https://github.com/wilx/log4cplus-trunk> > > The mirror is updated hourly by a cron job on my box, so it should be > fairly up to date. At this point, the mirror is one way only, from > SourceForge to Github. > Hi Václav, Can we now submit pull requests through github? > -- > VZ > > > > ------------------------------------------------------------------------------ > This SF.net email is sponsored by Windows: > > Build for Windows Store. > > http://p.sf.net/sfu/windows-dev2dev > _______________________________________________ > Log4cplus-devel mailing list > Log...@li... > https://lists.sourceforge.net/lists/listinfo/log4cplus-devel > > -- Best Regards, Sergei Nikulov |
|
From: Václav Z. <vha...@gm...> - 2013-07-04 06:19:40
|
Hi. Per popular request, I have set up a mirror of log4cplus trunk on Github: <https://github.com/wilx/log4cplus-trunk> The mirror is updated hourly by a cron job on my box, so it should be fairly up to date. At this point, the mirror is one way only, from SourceForge to Github. -- VZ |
|
From: Václav Z. <vha...@gm...> - 2013-07-03 20:48:12
|
Hi. I have released log4cplus 1.1.2-RC2. It contains small amount of bug fixes and improvements: - Fixed crash of DLL builds on Windows when _WIN32_WINNT>=0x0600. - Roll log file both before and after append to avoid logging into stale file when the log file has already been rolled by another logging process. - Known issue: Logging into a single log file from multiple processes on Windows breaks the rolling of the log files because open files cannot be renamed. - Fixed bug #166 - Close appender only once even when it is used by multiple loggers. -- VZ |
|
From: Václav Z. <vha...@gm...> - 2013-06-21 17:49:25
|
On 06/21/2013 07:29 AM, Stoll Ulrich, CH wrote: > I forgot to mention that I used the static lib. This one fails even with 1.1.1. > > In the meantime I switched to the dll and it works now. It is good to know it is not completely broken for use in a service. It would still be nice to know why it is failing for you. -- VZ > > -----Original Message----- > From: Václav Zeman [mailto:vha...@gm...] > Sent: Donnerstag, 20. Juni 2013 17:39 > To: Stoll Ulrich, CH > Cc: log...@li... > Subject: Re: [Log4cplus-devel] Windows Service exits with 0xc000007b > > On 20 June 2013 12:36, Stoll Ulrich, CH <Ulr...@au...> wrote: >> I have a Windows Service written VC10. It contains managed and >> unmanaged code. >> >> >> >> It works fine with log4cplus 1.0.4. However, after upgrading to >> log4cplus 1.1.0, it fails with 0xc000007b. > Is this failure at run time or during startup? IOW, does it even load the log4cplus.dll? If this is during run time, could you obtain a stack trace? > >> >> >> >> I need 1.1.0 or higher because of the syslog appender. > Have you tried 1.1.1? |
|
From: Stoll U. C. <Ulr...@au...> - 2013-06-21 05:29:29
|
I forgot to mention that I used the static lib. This one fails even with 1.1.1. In the meantime I switched to the dll and it works now. -----Original Message----- From: Václav Zeman [mailto:vha...@gm...] Sent: Donnerstag, 20. Juni 2013 17:39 To: Stoll Ulrich, CH Cc: log...@li... Subject: Re: [Log4cplus-devel] Windows Service exits with 0xc000007b On 20 June 2013 12:36, Stoll Ulrich, CH <Ulr...@au...> wrote: > I have a Windows Service written VC10. It contains managed and > unmanaged code. > > > > It works fine with log4cplus 1.0.4. However, after upgrading to > log4cplus 1.1.0, it fails with 0xc000007b. Is this failure at run time or during startup? IOW, does it even load the log4cplus.dll? If this is during run time, could you obtain a stack trace? > > > > I need 1.1.0 or higher because of the syslog appender. Have you tried 1.1.1? -- VZ "This e-mail, any associated files and the information contained in them are confidential and is intended for the addressee(s) only. If you have received this message in error please notify the originator and delete the email immediately. The unauthorised use, disclosure, copying or alteration of this message is strictly forbidden. E-mails to and from the company are monitored for operational reasons and in accordance with lawful business practices. Any opinions expressed are those of the individual and do not necessarily represent the views of the company. The company does not conclude contracts by email and all negotiations are subject to contract. We make every effort to maintain our network free from computer viruses but accept no responsibility for any viruses which might be transferred by this e-mail." |
|
From: Václav Z. <vha...@gm...> - 2013-06-20 15:38:44
|
On 20 June 2013 12:36, Stoll Ulrich, CH <Ulr...@au...> wrote: > I have a Windows Service written VC10. It contains managed and unmanaged > code. > > > > It works fine with log4cplus 1.0.4. However, after upgrading to log4cplus > 1.1.0, it fails with 0xc000007b. Is this failure at run time or during startup? IOW, does it even load the log4cplus.dll? If this is during run time, could you obtain a stack trace? > > > > I need 1.1.0 or higher because of the syslog appender. Have you tried 1.1.1? -- VZ |
|
From: Stoll U. C. <Ulr...@au...> - 2013-06-20 10:49:15
|
I have a Windows Service written VC10. It contains managed and unmanaged code. It works fine with log4cplus 1.0.4. However, after upgrading to log4cplus 1.1.0, it fails with 0xc000007b. I need 1.1.0 or higher because of the syslog appender. Any help is appreciated. Ulrich ________________________________ "This e-mail, any associated files and the information contained in them are confidential and is intended for the addressee(s) only. If you have received this message in error please notify the originator and delete the email immediately. The unauthorised use, disclosure, copying or alteration of this message is strictly forbidden. E-mails to and from the company are monitored for operational reasons and in accordance with lawful business practices. Any opinions expressed are those of the individual and do not necessarily represent the views of the company. The company does not conclude contracts by email and all negotiations are subject to contract. We make every effort to maintain our network free from computer viruses but accept no responsibility for any viruses which might be transferred by this e-mail." |
|
From: Václav Z. <vha...@gm...> - 2013-06-17 22:00:21
|
On 06/10/2013 08:08 PM, Jeremy C. Reed wrote:
> I noticed that I had a few processes still with open log files and when
> they logged they logged to the old log file instead of new file.
> This means that an admin may overlook it or, even worse, it may be
> rotated and lost.
Thank you for the problem report.
>
> Is this a feature?
This piece of code pre-dates my involvement. The old version of
log4cplus do not take multiple processes into account.
>
> Here is a workaround that seems to work for me:
>
> --- ./src/fileappender.cxx.orig 2013-06-07 11:43:19.000000000 -0500
> +++ ./src/fileappender.cxx 2013-06-07 11:45:06.000000000 -0500
> @@ -488,11 +488,13 @@
> void
> RollingFileAppender::append(const spi::InternalLoggingEvent& event)
> {
> - FileAppender::append(event);
>
> + // Rotate log file if needed before appending to it.
> if(out.tellp() > maxFileSize) {
> rollover(true);
> }
> +
> + FileAppender::append(event);
> }
It seems to me that we might need to extend the patch and add seek to
end of file before the roll condition and also to add second rotation
check after the FileAppender::append() call. The modified patch is
attached. I have committed this to both trunk and 1.1.x branches.
>
>
> This is with BIND10 which has many logging processes using a single
> log4cplus configuration. For information, see
> http://bind10.isc.org/ticket/1622#comment:34
> http://bind10.isc.org/ticket/2988
--
VZ
|
|
From: Jeremy C. R. <re...@re...> - 2013-06-10 18:08:19
|
I noticed that I had a few processes still with open log files and when
they logged they logged to the old log file instead of new file.
This means that an admin may overlook it or, even worse, it may be
rotated and lost.
Is this a feature?
Here is a workaround that seems to work for me:
--- ./src/fileappender.cxx.orig 2013-06-07 11:43:19.000000000 -0500
+++ ./src/fileappender.cxx 2013-06-07 11:45:06.000000000 -0500
@@ -488,11 +488,13 @@
void
RollingFileAppender::append(const spi::InternalLoggingEvent& event)
{
- FileAppender::append(event);
+ // Rotate log file if needed before appending to it.
if(out.tellp() > maxFileSize) {
rollover(true);
}
+
+ FileAppender::append(event);
}
This is with BIND10 which has many logging processes using a single
log4cplus configuration. For information, see
http://bind10.isc.org/ticket/1622#comment:34
http://bind10.isc.org/ticket/2988
Jeremy C. Reed
echo 'EhZ[h ^jjf0%%h[[Zc[Z_W$d[j%Xeeai%ZW[ced#]dk#f[d]k_d%' | \
tr '#-~' '\-.-{'
|
|
From: Václav Z. <vha...@gm...> - 2013-05-29 21:24:27
|
Hi. I have released log4cplus 1.1.2-RC1. The changes relative to 1.1.1 are one bug fix and a pair (--enable-so-version and --enable-release-version) of configure script options. It is now possible to build undecorated log4cplus.so, using the negative variants of the two options. log4cplus 1.1.2-RC1 - Fixed bug #163 - Initialization issue. - Added --enable-so-version and --enable-release-version configure script options to allow production of undecorated binaries. -- VZ |
|
From: Brice C. <Bri...@ce...> - 2013-05-24 12:58:14
|
Hello, >> I am attaching a patch (now part of both trunk and 1.1.x branch) that should allow you to >> configure log4cplus with --disable-so-version and --disable-release-version flags. >> The produces shared library is liblog4cplus.so (on Ubuntu). HTH. Thanks very much for your fast action, I have tested the 1.1.x branch on Ubuntu, Red Hat EL5 32 bits and 64 bits and it works fine. Just for info, we're looking into using log4cplus to perform logging inside the CERN middleware protocol (DIP) that allows the Large Hadron Collider (LHC) and the 4 major CERN experiments to exchange information and trigger particle observation data taking. Once we go to production, we would gladly join the list of satisfied Log4cplus users ! Cheers, Brice |
|
From: Václav Z. <vha...@gm...> - 2013-05-23 22:00:56
|
On 05/23/2013 03:25 PM, Brice Copy wrote: > Hello, Hi. > > > > I am compiling log4cplus from source on Red Hat enterprise 5 (CERN > scientific linux) 32 and 64 bits. > > > > The point is to package Log4cplus in my Java webstart project (to enable > logging in a native C++ library). > > > > The problem is that when I use the configure and make scripts, it > produces a liblog4cplus-1.1.so.5 library file. > > > > I really need the library file that ends with “.so” - or Java webstart > will not unpack it from the native library JAR package and add it to the > library path. > > > > Renaming the file to liblog4cplus-1.1.so does not work, because I link > my own native library to log4cplus, and the liblog4cplus-1.1.so.5 file > contains the SONAME set to “liblog4cplus-1.1.so.5” (so the linker will > link to liblog4cplus-1.1.so but my own library expects > liblog4cplus-1.1.so.5 to be present on the path). > > > > Is there a “configure” option I can use to force the SONAME to > liblog4cplus-1.1.so ? > > Or can I strip the SONAME from the final library, thereby forcing the > linker to link to the library file name liblog4cplus-1.1.so ? I am attaching a patch (now part of both trunk and 1.1.x branch) that should allow you to configure log4cplus with --disable-so-version and --disable-release-version flags. The produces shared library is liblog4cplus.so (on Ubuntu). HTH. -- VZ |
927 messages has been excluded from this view by a project administrator.
