log4cplus-devel — Mailing list for log4cplus developers

[Log4cplus-devel] [log4cplus] testsuite: 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 failed

[Hilton F. <hil...@gm...>]

 Dear all,

I would like to work with log4cplus, but I'm facing some problems.

Please find attached the result of the tests, as you asked for.

I have copied ThreadPool.h from your project to the directory threadpool in
log4cplus folder.

Then I did a simple configure, with

./configure --enable-debug

followed by the default make:
make

and then
make check

All the best,
Hilton

[Log4cplus-devel] log4cplus 2.0.0 released

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

I have released log4cplus version 2.0.0. There are only minor changes
compared to last release candidate:

  - CMake improvements: Automate export of includes if building as Cmake
sub-module. (Rodion Malinovsky)

  - Debian spec file improvements: Use parallel build. Fix installation
path on 64bit. (Michal Marek)

  - CMake improvements: Use `${CMAKE_INSTALL_LIBDIR}` instead of
hardcoding lib. (Radek Dostál)

  - Experimental Windows 10 ARM support through CMAKE


-- 
VH

Re: [Log4cplus-devel] State of log4cplus 1.x vs. 2.x

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

On 26 March 2018 at 17:21, <Sim...@bt...> wrote:

> Hi,
>
>
>
> I would like to implement an adapter from our internal Logging API to
> log4cplus, and I am unsure which version to target. Log4cplus 2.0 has not
> been released yet, but I would prefer to use that as a target if it is
> likely to be released in the next months. What needs to be done for
> log4cplus to be released? Maybe I could assist in getting it done as soon I
> have a running prototype adapter.
>
>
>
> If there are major obstacles in releasing 2.0, I would probably better
> stick with 1.2.x for now, right?
>

​Well, there have not been any significant changes on the 2.0.x ​branch for
some time. I could probably just release it as it is now. If you could try
using 2.0.x branch, that would be awesome. If you do not encounter
initialization or destruction issues or leaks then I think the branch is
releasable.



>
>
> Best regards
>
>
> i.A. Simon Giesecke
> BU Operations
> Smart Market
> Senior Consultant
>
> BTC Business Technology Consulting AG
>
> Kurfürstendamm 33
>
> 10719 Berlin
>
> Tel:      +49 441 3612-4826 <+49%20441%2036124826>
> Mobil:   +49 174 9081611 <+49%20174%209081611>
> Fax:     +49 441 3612-3999 <+49%20441%2036123999>
> E-Mail:  Sim...@bt...
> Web:     www.btc-ag.com
>
>
> Rechtliche Hinweise:
>
> www.btc-ag.com/impressum.htm
>
> Handelsregister: Amtsgericht Oldenburg HRB 4717
>
> Aufsichtsratsvorsitzender: Michael Heidkamp
>
> Vorstand: Dr. Jörg Ritter, Dirk Thole
>
>
>
>
-- 
VH

[Log4cplus-devel] State of log4cplus 1.x vs. 2.x

[<Sim...@bt...>]

Hi,

I would like to implement an adapter from our internal Logging API to log4cplus, and I am unsure which version to target. Log4cplus 2.0 has not been released yet, but I would prefer to use that as a target if it is likely to be released in the next months. What needs to be done for log4cplus to be released? Maybe I could assist in getting it done as soon I have a running prototype adapter.

If there are major obstacles in releasing 2.0, I would probably better stick with 1.2.x for now, right?

Best regards

i.A. Simon Giesecke
BU Operations
Smart Market
Senior Consultant

BTC Business Technology Consulting AG
Kurfürstendamm 33
10719 Berlin
Tel:      +49 441 3612-4826
Mobil:   +49 174 9081611
Fax:     +49 441 3612-3999
E-Mail:  Sim...@bt...
Web:     www.btc-ag.com

Rechtliche Hinweise:
www.btc-ag.com/impressum.htm
Handelsregister: Amtsgericht Oldenburg HRB 4717
Aufsichtsratsvorsitzender: Michael Heidkamp
Vorstand: Dr. Jörg Ritter, Dirk Thole

[Log4cplus-devel] log4cplus 1.2.1 released

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

Hi everyone.

I have released log4cplus version 1.2.1. Version 1.2.1 is virtually
identical to 1.2.1-RC2. This version is signed with new key:
E406292F7D08BBB00846131404B89D51DFE5A215. The previous DSA key was only
1024 bits long.

-- 
VH

[Log4cplus-devel] Memory "leak"

[<qu...@no...>]

Hello,

I just arrived on a big project, and I am supposed to resolve a memory
problem related to log4cplus. Each time an event is logged, the RAM
raises, the message is logged, but doesn't lowers afterwards. So, after
some time, the system RAM is exhausted. But when I stop the app, the
memory is released.

It is not easy at all to investigate : theproject is huge, and the build
complex. I found the guilty instruction (a wrapped call to log4cplus), but
I didn't succeed to go farther. I even tried a call to threadCleanup().

What could explain a such behavior ? Log4cplus is statically linked.
By investigating in the code of log4cplus, I saw how the messages are
added to the appenders, but I don't see where they are consumed, in order
to check if the memory which has been assigned for them is actually freed.

Thanks for help.

Re: [Log4cplus-devel] log4cplus // source locality

[Sergei N. <ser...@gm...>]

2017-07-26 14:37 GMT+03:00 Václav Haisman <vha...@gm...>:
> On 26 July 2017 at 12:21, Sergei Nikulov wrote:
>> Hello Václav,
>>
>> What I liked about 1.x.x - possibility to use it without any links to
>> GitHub from the local clone.
>> But times flies and I try to use 2.x.x in my project (new compilers
>> complains too much about auto_ptr).
>>
>> On 2.x.x branch you've added submodules for catch and threadpool.
>>
>> Is it possible not using submodules in 2.x.x line?
>> Was it some unresolvable requirement to add those links?
>>
>> Thank you.
>
> I have added the submodules because that allows me to update them
> without much hassle that in-tree maintenance of imported sources would
> bring. Threadpool is required so that all logging requests can be
> handled asynchronously. Catch is required for unit tests
> implementation.
>
> What is your objection to using submodules?

I prefer have self-contained sources, without any links to external
repositories.
The only objection - I need a live internet connection to GitHub even
if I clone log4cplus from local folder/mirror.

It is no big deal, but it complicates things a bit for only 2 files added.

Catch can be added without any issues as a single file (or even
downloaded when tests enabled).
Threadpool also not changed since 2015, so can be "frozen" within the
repository.

>
> --
> VH



-- 
Best Regards,
Sergei Nikulov

Re: [Log4cplus-devel] log4cplus // source locality

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

On 26 July 2017 at 12:21, Sergei Nikulov wrote:
> Hello Václav,
>
> What I liked about 1.x.x - possibility to use it without any links to
> GitHub from the local clone.
> But times flies and I try to use 2.x.x in my project (new compilers
> complains too much about auto_ptr).
>
> On 2.x.x branch you've added submodules for catch and threadpool.
>
> Is it possible not using submodules in 2.x.x line?
> Was it some unresolvable requirement to add those links?
>
> Thank you.

I have added the submodules because that allows me to update them
without much hassle that in-tree maintenance of imported sources would
bring. Threadpool is required so that all logging requests can be
handled asynchronously. Catch is required for unit tests
implementation.

What is your objection to using submodules?

--
VH

[Log4cplus-devel] log4cplus // source locality

[Sergei N. <ser...@gm...>]

Hello Václav,

What I liked about 1.x.x - possibility to use it without any links to
GitHub from the local clone.
But times flies and I try to use 2.x.x in my project (new compilers
complains too much about auto_ptr).

On 2.x.x branch you've added submodules for catch and threadpool.

Is it possible not using submodules in 2.x.x line?
Was it some unresolvable requirement to add those links?

Thank you.

-- 
Best Regards,
Sergei Nikulov

[Log4cplus-devel] [log4cplus:bugs] #343 Crash on app exit

[Václav H. <wi...@us...>]

- **labels**: java, v1.2.0, c++11, threads, mutex --> java, v1.2.0, c++11, threads, mutex, fixed
- **status**: open --> closed



---

** [bugs:#343] Crash on app exit**

**Status:** closed
**Group:** v1.2.0
**Labels:** java v1.2.0 c++11 threads mutex fixed 
**Created:** Fri Jun 23, 2017 03:02 PM UTC by Ralf Sieger
**Last Updated:** Wed Jul 12, 2017 10:54 AM UTC
**Owner:** Václav Haisman
**Attachments:**

- [log4cplus_debug_hs_err_pid11184.log](https://sourceforge.net/p/log4cplus/bugs/343/attachment/log4cplus_debug_hs_err_pid11184.log) (23.5 kB; application/octet-stream)
- [log4cplus_release_hs_err_pid10836.log](https://sourceforge.net/p/log4cplus/bugs/343/attachment/log4cplus_release_hs_err_pid10836.log) (23.9 kB; application/octet-stream)


log4cplus:

* 1.2.0
* Visual Studio 2012
* config: release and debug
* windows 10, i7 4770

client:

* 32 bit Java 7 application
* log4cplus as dll
* log4cplus.lib and log4cplusD.lib
* multibyte chars
* see attached logfiles
* client DLL compile settings: no MFC, no ATL, multibyte charset, /MDd and /MD

We use log4cplus in an custom C++ dll which itself gets dynamically loaded in java program.
during the runtime everything works ok.
At application exit we see an java hotspot error (see logs). 
This happens with and without calling `log4cplus::Logger::shutdown();`
The problem also occurs if nothing but `log4cplus::initialize();` and `log4cplus::Logger::shutdown();` are called.

From the hotspot error it looks like an cleanup issue:

~~~
Stack: [0x46760000,0x467b0000],  sp=0x467aee5c,  free space=315k
Native frames: (J=compiled Java code, j=interpreted, Vv=VM code, C=native code)
C  [ntdll.dll+0xecc94]
C  [ntdll.dll+0x9683a]
C  [KERNEL32.DLL+0x1dbb9]
C  [MSVCR110.dll+0x9fa77]
C  [MSVCR110.dll+0x4defc]
C  [MSVCR110.dll+0x4f4cf]
C  [MSVCR110.dll+0x2431b]
C  [MSVCR110.dll+0x243dc]
C  [MSVCR110.dll+0x16629]
C  [MSVCR110.dll+0x6a312]
C  [MSVCP110.dll+0x2e2d8]
C  [MSVCP110.dll+0x2e47e]
C  [log4cplus.dll+0x229b]  log4cplus::thread::SyncGuard<log4cplus::thread::Mutex>::SyncGuard<log4cplus::thread::Mutex>+0x2b
C  [log4cplus.dll+0x3f1dd]  log4cplus::spi::ObjectRegistryBase::clear+0x2d
C  [log4cplus.dll+0x14225]  log4cplus::`anonymous namespace'::DefaultContext::~DefaultContext+0x45
C  [log4cplus.dll+0x143a5]  log4cplus::`anonymous namespace'::destroy_default_context::~destroy_default_context+0x25
C  [log4cplus.dll+0x559cd]  log4cplus::`anonymous namespace'::`dynamic atexit destructor for 'destroy_default_context_''+0xd
C  [log4cplus.dll+0x4e002]  _CRT_INIT+0xc1
C  [log4cplus.dll+0x4e228]  __DllMainCRTStartup+0xcf
C  [log4cplus.dll+0x4e152]  _DllMainCRTStartup+0x1c
~~~


---

Sent from sourceforge.net because log...@li... is subscribed to https://sourceforge.net/p/log4cplus/bugs/

To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/log4cplus/admin/bugs/options.  Or, if this is a mailing list, you can unsubscribe from the mailing list.

[Log4cplus-devel] [log4cplus:bugs] #343 Crash on app exit

[Ralf S. <ral...@us...>]

Hi Václav,
I've tried your patch with log4cplus-1.2.1-rc2 and it seems this did the trick!
Thank you very much for the quick fix!


---

** [bugs:#343] Crash on app exit**

**Status:** open
**Group:** v1.2.0
**Labels:** java v1.2.0 c++11 threads mutex 
**Created:** Fri Jun 23, 2017 03:02 PM UTC by Ralf Sieger
**Last Updated:** Tue Jul 11, 2017 04:57 PM UTC
**Owner:** Václav Haisman
**Attachments:**

- [log4cplus_debug_hs_err_pid11184.log](https://sourceforge.net/p/log4cplus/bugs/343/attachment/log4cplus_debug_hs_err_pid11184.log) (23.5 kB; application/octet-stream)
- [log4cplus_release_hs_err_pid10836.log](https://sourceforge.net/p/log4cplus/bugs/343/attachment/log4cplus_release_hs_err_pid10836.log) (23.9 kB; application/octet-stream)


log4cplus:

* 1.2.0
* Visual Studio 2012
* config: release and debug
* windows 10, i7 4770

client:

* 32 bit Java 7 application
* log4cplus as dll
* log4cplus.lib and log4cplusD.lib
* multibyte chars
* see attached logfiles
* client DLL compile settings: no MFC, no ATL, multibyte charset, /MDd and /MD

We use log4cplus in an custom C++ dll which itself gets dynamically loaded in java program.
during the runtime everything works ok.
At application exit we see an java hotspot error (see logs). 
This happens with and without calling `log4cplus::Logger::shutdown();`
The problem also occurs if nothing but `log4cplus::initialize();` and `log4cplus::Logger::shutdown();` are called.

From the hotspot error it looks like an cleanup issue:

~~~
Stack: [0x46760000,0x467b0000],  sp=0x467aee5c,  free space=315k
Native frames: (J=compiled Java code, j=interpreted, Vv=VM code, C=native code)
C  [ntdll.dll+0xecc94]
C  [ntdll.dll+0x9683a]
C  [KERNEL32.DLL+0x1dbb9]
C  [MSVCR110.dll+0x9fa77]
C  [MSVCR110.dll+0x4defc]
C  [MSVCR110.dll+0x4f4cf]
C  [MSVCR110.dll+0x2431b]
C  [MSVCR110.dll+0x243dc]
C  [MSVCR110.dll+0x16629]
C  [MSVCR110.dll+0x6a312]
C  [MSVCP110.dll+0x2e2d8]
C  [MSVCP110.dll+0x2e47e]
C  [log4cplus.dll+0x229b]  log4cplus::thread::SyncGuard<log4cplus::thread::Mutex>::SyncGuard<log4cplus::thread::Mutex>+0x2b
C  [log4cplus.dll+0x3f1dd]  log4cplus::spi::ObjectRegistryBase::clear+0x2d
C  [log4cplus.dll+0x14225]  log4cplus::`anonymous namespace'::DefaultContext::~DefaultContext+0x45
C  [log4cplus.dll+0x143a5]  log4cplus::`anonymous namespace'::destroy_default_context::~destroy_default_context+0x25
C  [log4cplus.dll+0x559cd]  log4cplus::`anonymous namespace'::`dynamic atexit destructor for 'destroy_default_context_''+0xd
C  [log4cplus.dll+0x4e002]  _CRT_INIT+0xc1
C  [log4cplus.dll+0x4e228]  __DllMainCRTStartup+0xcf
C  [log4cplus.dll+0x4e152]  _DllMainCRTStartup+0x1c
~~~


---

Sent from sourceforge.net because log...@li... is subscribed to https://sourceforge.net/p/log4cplus/bugs/

To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/log4cplus/admin/bugs/options.  Or, if this is a mailing list, you can unsubscribe from the mailing list.

[Log4cplus-devel] log4cplus 1.1.3-RC8 released

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

I have released log4cplus 1.1.3-RC8:

   -

   Fixed GitHub issue #195. Check if queue thread pointer is not NULL and
   if it is running before trying to join it.
   -

   Fixed GitHub issue #205. Fixed NULL pointer dereference of queue in
   AsyncAppender code.
   -

   Fixed SF#333. AsyncAppender‘s appenders need to be closed so that
   accumulated logs get flushed onto disk.
   -

   Updated android.toolchain.cmake from OpenCV.
   -

   Fixed GitHub issue #215. Mark ~HierarchyLocker() with noexcept(false) to
   avoid unlikely but possible terminate() call and a warning message
   during compilation.
   -

   Disabled TLS support for iOS.
   -

   Do not use language level thread-local storage on Cygwin. (GCC PR64697).
   -

   Allow filters cofiguration in AsyncAppender. (suggested in SF#297 by
   Markus von Arx)
   -

   Handle SocketBuffer overflow by throwing exception.

​
-- 
VH

[Log4cplus-devel] log4cplus 1.2.1-RC1 released

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

Hi.

I have released log4cplus 1.2.1-RC2:

  - Fixed SF#334. Handle signal interrupting `sem_wait()`.

  - Avoid language level thread-local variables on Cygwin to avoid
compilation issue (GCC PR64697).

  - Implement suggestion in SF#297 to allow filters in `AsyncAppender`
configuration.

  - Require CMake 2.8.12 and later due to use of `INCLUDES DE
STINATION` (Patched by Enrico Jorns.)

  - Fixed GitHub bug #136, again. Use `mktime()`'s ability to adjust
for excess values in fields of `struct tm`.

  - `SocketBuffer` now throws an exception on overflow and
`SocketAppender` handl
es it and does not send overlong messages.

  - Fixed SF#343. Avoid using C++11 `std::mutex` and other
synchronization primitives in Visual Studio earlier than 2015.


-- 
VH

[Log4cplus-devel] [log4cplus:bugs] #343 Crash on app exit

[Václav H. <wi...@us...>]

I have pushed [bd27044f35](https://github.com/wilx/log4cplus/commit/bd27044f353f977dfc35da1a5157a2b42f94112c) to 1.2.x branch to work around this for 1.2.x. It should actually be OK on 2.0.x branch as only Visual Studio 2015 and later is supported there.


---

** [bugs:#343] Crash on app exit**

**Status:** open
**Group:** v1.2.0
**Labels:** java v1.2.0 c++11 threads mutex 
**Created:** Fri Jun 23, 2017 03:02 PM UTC by Ralf Sieger
**Last Updated:** Tue Jul 11, 2017 03:00 PM UTC
**Owner:** Václav Haisman
**Attachments:**

- [log4cplus_debug_hs_err_pid11184.log](https://sourceforge.net/p/log4cplus/bugs/343/attachment/log4cplus_debug_hs_err_pid11184.log) (23.5 kB; application/octet-stream)
- [log4cplus_release_hs_err_pid10836.log](https://sourceforge.net/p/log4cplus/bugs/343/attachment/log4cplus_release_hs_err_pid10836.log) (23.9 kB; application/octet-stream)


log4cplus:

* 1.2.0
* Visual Studio 2012
* config: release and debug
* windows 10, i7 4770

client:

* 32 bit Java 7 application
* log4cplus as dll
* log4cplus.lib and log4cplusD.lib
* multibyte chars
* see attached logfiles
* client DLL compile settings: no MFC, no ATL, multibyte charset, /MDd and /MD

We use log4cplus in an custom C++ dll which itself gets dynamically loaded in java program.
during the runtime everything works ok.
At application exit we see an java hotspot error (see logs). 
This happens with and without calling `log4cplus::Logger::shutdown();`
The problem also occurs if nothing but `log4cplus::initialize();` and `log4cplus::Logger::shutdown();` are called.

From the hotspot error it looks like an cleanup issue:

~~~
Stack: [0x46760000,0x467b0000],  sp=0x467aee5c,  free space=315k
Native frames: (J=compiled Java code, j=interpreted, Vv=VM code, C=native code)
C  [ntdll.dll+0xecc94]
C  [ntdll.dll+0x9683a]
C  [KERNEL32.DLL+0x1dbb9]
C  [MSVCR110.dll+0x9fa77]
C  [MSVCR110.dll+0x4defc]
C  [MSVCR110.dll+0x4f4cf]
C  [MSVCR110.dll+0x2431b]
C  [MSVCR110.dll+0x243dc]
C  [MSVCR110.dll+0x16629]
C  [MSVCR110.dll+0x6a312]
C  [MSVCP110.dll+0x2e2d8]
C  [MSVCP110.dll+0x2e47e]
C  [log4cplus.dll+0x229b]  log4cplus::thread::SyncGuard<log4cplus::thread::Mutex>::SyncGuard<log4cplus::thread::Mutex>+0x2b
C  [log4cplus.dll+0x3f1dd]  log4cplus::spi::ObjectRegistryBase::clear+0x2d
C  [log4cplus.dll+0x14225]  log4cplus::`anonymous namespace'::DefaultContext::~DefaultContext+0x45
C  [log4cplus.dll+0x143a5]  log4cplus::`anonymous namespace'::destroy_default_context::~destroy_default_context+0x25
C  [log4cplus.dll+0x559cd]  log4cplus::`anonymous namespace'::`dynamic atexit destructor for 'destroy_default_context_''+0xd
C  [log4cplus.dll+0x4e002]  _CRT_INIT+0xc1
C  [log4cplus.dll+0x4e228]  __DllMainCRTStartup+0xcf
C  [log4cplus.dll+0x4e152]  _DllMainCRTStartup+0x1c
~~~


---

Sent from sourceforge.net because log...@li... is subscribed to https://sourceforge.net/p/log4cplus/bugs/

To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/log4cplus/admin/bugs/options.  Or, if this is a mailing list, you can unsubscribe from the mailing list.

[Log4cplus-devel] [log4cplus:bugs] #343 Crash on app exit

[Václav H. <wi...@us...>]

This is basically the issue: https://stackoverflow.com/questions/22402791/visual-studio-2013-stdmutex-and-the-dreaded-windows-loader-lock

I wonder, could you try it with Visual Studio 2015 or 2017?



---

** [bugs:#343] Crash on app exit**

**Status:** open
**Group:** v1.2.0
**Labels:** java v1.2.0 c++11 threads mutex 
**Created:** Fri Jun 23, 2017 03:02 PM UTC by Ralf Sieger
**Last Updated:** Tue Jul 11, 2017 02:31 PM UTC
**Owner:** Václav Haisman
**Attachments:**

- [log4cplus_debug_hs_err_pid11184.log](https://sourceforge.net/p/log4cplus/bugs/343/attachment/log4cplus_debug_hs_err_pid11184.log) (23.5 kB; application/octet-stream)
- [log4cplus_release_hs_err_pid10836.log](https://sourceforge.net/p/log4cplus/bugs/343/attachment/log4cplus_release_hs_err_pid10836.log) (23.9 kB; application/octet-stream)


log4cplus:

* 1.2.0
* Visual Studio 2012
* config: release and debug
* windows 10, i7 4770

client:

* 32 bit Java 7 application
* log4cplus as dll
* log4cplus.lib and log4cplusD.lib
* multibyte chars
* see attached logfiles
* client DLL compile settings: no MFC, no ATL, multibyte charset, /MDd and /MD

We use log4cplus in an custom C++ dll which itself gets dynamically loaded in java program.
during the runtime everything works ok.
At application exit we see an java hotspot error (see logs). 
This happens with and without calling `log4cplus::Logger::shutdown();`
The problem also occurs if nothing but `log4cplus::initialize();` and `log4cplus::Logger::shutdown();` are called.

From the hotspot error it looks like an cleanup issue:

~~~
Stack: [0x46760000,0x467b0000],  sp=0x467aee5c,  free space=315k
Native frames: (J=compiled Java code, j=interpreted, Vv=VM code, C=native code)
C  [ntdll.dll+0xecc94]
C  [ntdll.dll+0x9683a]
C  [KERNEL32.DLL+0x1dbb9]
C  [MSVCR110.dll+0x9fa77]
C  [MSVCR110.dll+0x4defc]
C  [MSVCR110.dll+0x4f4cf]
C  [MSVCR110.dll+0x2431b]
C  [MSVCR110.dll+0x243dc]
C  [MSVCR110.dll+0x16629]
C  [MSVCR110.dll+0x6a312]
C  [MSVCP110.dll+0x2e2d8]
C  [MSVCP110.dll+0x2e47e]
C  [log4cplus.dll+0x229b]  log4cplus::thread::SyncGuard<log4cplus::thread::Mutex>::SyncGuard<log4cplus::thread::Mutex>+0x2b
C  [log4cplus.dll+0x3f1dd]  log4cplus::spi::ObjectRegistryBase::clear+0x2d
C  [log4cplus.dll+0x14225]  log4cplus::`anonymous namespace'::DefaultContext::~DefaultContext+0x45
C  [log4cplus.dll+0x143a5]  log4cplus::`anonymous namespace'::destroy_default_context::~destroy_default_context+0x25
C  [log4cplus.dll+0x559cd]  log4cplus::`anonymous namespace'::`dynamic atexit destructor for 'destroy_default_context_''+0xd
C  [log4cplus.dll+0x4e002]  _CRT_INIT+0xc1
C  [log4cplus.dll+0x4e228]  __DllMainCRTStartup+0xcf
C  [log4cplus.dll+0x4e152]  _DllMainCRTStartup+0x1c
~~~


---

Sent from sourceforge.net because log...@li... is subscribed to https://sourceforge.net/p/log4cplus/bugs/

To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/log4cplus/admin/bugs/options.  Or, if this is a mailing list, you can unsubscribe from the mailing list.

[Log4cplus-devel] [log4cplus:bugs] #317 Cannot compile a Single Threaded version and the Simple Server simultaneously.

[Václav H. <wi...@us...>]

- **labels**: cmake, thread, simpleserver --> cmake, simpleserver, threads



---

** [bugs:#317] Cannot compile a Single Threaded version and the Simple Server simultaneously.**

**Status:** closed
**Group:** v1.2.x
**Labels:** cmake simpleserver threads 
**Created:** Thu May 28, 2015 06:09 AM UTC by Alexis Wilke
**Last Updated:** Thu May 28, 2015 09:54 AM UTC
**Owner:** Václav Haisman
**Attachments:**

- [0001-log4cplus-1.2.0-rc3.patch](https://sourceforge.net/p/log4cplus/bugs/317/attachment/0001-log4cplus-1.2.0-rc3.patch) (624 Bytes; text/x-patch)


I initialized the compilation environment using both: the simple server and the single threaded flags on.

    mkdir BUILD
    cd BUILD
    cmake -DLOG4CPLUS_SINGLE_THREADED=OFF ../log4cplus

Unfortunately, the simple server makes use of threads:

    class ClientThread : public log4cplus::thread::AbstractThread
    ...

It seems to me that you could test and err in the main cmake so we don't get a surprise at the end.

There is what I propose:

    --- a/log4cplus-1.2.0-rc3/CMakeLists.txt	2015-01-04 06:42:13.904962796 -0800
    +++ b/log4cplus/CMakeLists.txt	2015-05-27 22:48:13.802072656 -0700
    @@ -33,6 +33,10 @@
       message (STATUS "Threads: ${CMAKE_THREAD_LIBS_INIT}")
     endif(NOT LOG4CPLUS_SINGLE_THREADED)
 
    +if(LOG4CPLUS_SINGLE_THREADED AND LOG4CPLUS_BUILD_LOGGINGSERVER)
    +  message (FATAL_ERROR "The logging server requires the multi-thread capability.")
    +endif(LOG4CPLUS_SINGLE_THREADED AND LOG4CPLUS_BUILD_LOGGINGSERVER)
    +
     set(BUILD_SHARED_LIBS TRUE CACHE BOOL "If TRUE, log4cplus is built as a shared library, otherwise as a static library")
     
     if (WIN32)




---

Sent from sourceforge.net because log...@li... is subscribed to https://sourceforge.net/p/log4cplus/bugs/

To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/log4cplus/admin/bugs/options.  Or, if this is a mailing list, you can unsubscribe from the mailing list.

[Log4cplus-devel] [log4cplus:bugs] #343 Crash on app exit

[Václav H. <wi...@us...>]

- **labels**: java, v1.2.0 --> java, v1.2.0, c++11, threads, mutex
- Description has changed:

Diff:

~~~~

--- old
+++ new
@@ -1,24 +1,27 @@
 log4cplus:
-- 1.2.0
-- Visual Studio 2012
-- config: release and debug
-- windows 10, i7 4770
+
+* 1.2.0
+* Visual Studio 2012
+* config: release and debug
+* windows 10, i7 4770
 
 client:
-- 32 bit Java 7 application
-- log4cplus as dll
-- log4cplus.lib and log4cplusD.lib
-- multibyte chars
-- see attached logfiles
-- client DLL compile settings: no MFC, no ATL, multibyte charset, /MDd and /MD
+
+* 32 bit Java 7 application
+* log4cplus as dll
+* log4cplus.lib and log4cplusD.lib
+* multibyte chars
+* see attached logfiles
+* client DLL compile settings: no MFC, no ATL, multibyte charset, /MDd and /MD
 
 We use log4cplus in an custom C++ dll which itself gets dynamically loaded in java program.
 during the runtime everything works ok.
 At application exit we see an java hotspot error (see logs). 
-This happens with and without calling log4cplus::Logger::shutdown();
-The problem also occurs if nothing but log4cplus::initialize(); and log4cplus::Logger::shutdown(); are called.
+This happens with and without calling `log4cplus::Logger::shutdown();`
+The problem also occurs if nothing but `log4cplus::initialize();` and `log4cplus::Logger::shutdown();` are called.
 
 From the hotspot error it looks like an cleanup issue:
+
 ~~~
 Stack: [0x46760000,0x467b0000],  sp=0x467aee5c,  free space=315k
 Native frames: (J=compiled Java code, j=interpreted, Vv=VM code, C=native code)

~~~~




---

** [bugs:#343] Crash on app exit**

**Status:** open
**Group:** v1.2.0
**Labels:** java v1.2.0 c++11 threads mutex 
**Created:** Fri Jun 23, 2017 03:02 PM UTC by Ralf Sieger
**Last Updated:** Tue Jul 11, 2017 02:29 PM UTC
**Owner:** Václav Haisman
**Attachments:**

- [log4cplus_debug_hs_err_pid11184.log](https://sourceforge.net/p/log4cplus/bugs/343/attachment/log4cplus_debug_hs_err_pid11184.log) (23.5 kB; application/octet-stream)
- [log4cplus_release_hs_err_pid10836.log](https://sourceforge.net/p/log4cplus/bugs/343/attachment/log4cplus_release_hs_err_pid10836.log) (23.9 kB; application/octet-stream)


log4cplus:

* 1.2.0
* Visual Studio 2012
* config: release and debug
* windows 10, i7 4770

client:

* 32 bit Java 7 application
* log4cplus as dll
* log4cplus.lib and log4cplusD.lib
* multibyte chars
* see attached logfiles
* client DLL compile settings: no MFC, no ATL, multibyte charset, /MDd and /MD

We use log4cplus in an custom C++ dll which itself gets dynamically loaded in java program.
during the runtime everything works ok.
At application exit we see an java hotspot error (see logs). 
This happens with and without calling `log4cplus::Logger::shutdown();`
The problem also occurs if nothing but `log4cplus::initialize();` and `log4cplus::Logger::shutdown();` are called.

From the hotspot error it looks like an cleanup issue:

~~~
Stack: [0x46760000,0x467b0000],  sp=0x467aee5c,  free space=315k
Native frames: (J=compiled Java code, j=interpreted, Vv=VM code, C=native code)
C  [ntdll.dll+0xecc94]
C  [ntdll.dll+0x9683a]
C  [KERNEL32.DLL+0x1dbb9]
C  [MSVCR110.dll+0x9fa77]
C  [MSVCR110.dll+0x4defc]
C  [MSVCR110.dll+0x4f4cf]
C  [MSVCR110.dll+0x2431b]
C  [MSVCR110.dll+0x243dc]
C  [MSVCR110.dll+0x16629]
C  [MSVCR110.dll+0x6a312]
C  [MSVCP110.dll+0x2e2d8]
C  [MSVCP110.dll+0x2e47e]
C  [log4cplus.dll+0x229b]  log4cplus::thread::SyncGuard<log4cplus::thread::Mutex>::SyncGuard<log4cplus::thread::Mutex>+0x2b
C  [log4cplus.dll+0x3f1dd]  log4cplus::spi::ObjectRegistryBase::clear+0x2d
C  [log4cplus.dll+0x14225]  log4cplus::`anonymous namespace'::DefaultContext::~DefaultContext+0x45
C  [log4cplus.dll+0x143a5]  log4cplus::`anonymous namespace'::destroy_default_context::~destroy_default_context+0x25
C  [log4cplus.dll+0x559cd]  log4cplus::`anonymous namespace'::`dynamic atexit destructor for 'destroy_default_context_''+0xd
C  [log4cplus.dll+0x4e002]  _CRT_INIT+0xc1
C  [log4cplus.dll+0x4e228]  __DllMainCRTStartup+0xcf
C  [log4cplus.dll+0x4e152]  _DllMainCRTStartup+0x1c
~~~


---

Sent from sourceforge.net because log...@li... is subscribed to https://sourceforge.net/p/log4cplus/bugs/

To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/log4cplus/admin/bugs/options.  Or, if this is a mailing list, you can unsubscribe from the mailing list.

[Log4cplus-devel] [log4cplus:bugs] #343 Crash on app exit

[Václav H. <wi...@us...>]

Thank you for the additional information, I think I now understand the situation. We have seen this before. The issue is with how are C++11 synchornization primitives implemented in Visual Studio.

As a stop gap measure, you can modify the log4cplus source like the following diff, for 1.2.x branch:

```diff
diff --git a/include/log4cplus/config/win32.h b/include/log4cplus/config/win32.h
index 8e5175cd..aa4b0202 100644
--- a/include/log4cplus/config/win32.h
+++ b/include/log4cplus/config/win32.h
@@ -162,7 +162,7 @@
 #  endif
 #  if _MSC_VER >= 1700
 #    define LOG4CPLUS_HAVE_CXX11_ATOMICS
-#    define LOG4CPLUS_WITH_CXX11_THREADS
+//#    define LOG4CPLUS_WITH_CXX11_THREADS
 #  endif
 #endif
```

This will however not apply on 2.0.x branch because I have removed the non-C++11 implementations of synchornization primitives. I will either have to re-introduce them or...I do not know what else yet.

I am keeping this open to remind me about this issue.


---

** [bugs:#343] Crash on app exit**

**Status:** open
**Group:** v1.2.0
**Labels:** java v1.2.0 
**Created:** Fri Jun 23, 2017 03:02 PM UTC by Ralf Sieger
**Last Updated:** Tue Jul 11, 2017 12:33 PM UTC
**Owner:** Václav Haisman
**Attachments:**

- [log4cplus_debug_hs_err_pid11184.log](https://sourceforge.net/p/log4cplus/bugs/343/attachment/log4cplus_debug_hs_err_pid11184.log) (23.5 kB; application/octet-stream)
- [log4cplus_release_hs_err_pid10836.log](https://sourceforge.net/p/log4cplus/bugs/343/attachment/log4cplus_release_hs_err_pid10836.log) (23.9 kB; application/octet-stream)


log4cplus:
- 1.2.0
- Visual Studio 2012
- config: release and debug
- windows 10, i7 4770

client:
- 32 bit Java 7 application
- log4cplus as dll
- log4cplus.lib and log4cplusD.lib
- multibyte chars
- see attached logfiles
- client DLL compile settings: no MFC, no ATL, multibyte charset, /MDd and /MD

We use log4cplus in an custom C++ dll which itself gets dynamically loaded in java program.
during the runtime everything works ok.
At application exit we see an java hotspot error (see logs). 
This happens with and without calling log4cplus::Logger::shutdown();
The problem also occurs if nothing but log4cplus::initialize(); and log4cplus::Logger::shutdown(); are called.

From the hotspot error it looks like an cleanup issue:
~~~
Stack: [0x46760000,0x467b0000],  sp=0x467aee5c,  free space=315k
Native frames: (J=compiled Java code, j=interpreted, Vv=VM code, C=native code)
C  [ntdll.dll+0xecc94]
C  [ntdll.dll+0x9683a]
C  [KERNEL32.DLL+0x1dbb9]
C  [MSVCR110.dll+0x9fa77]
C  [MSVCR110.dll+0x4defc]
C  [MSVCR110.dll+0x4f4cf]
C  [MSVCR110.dll+0x2431b]
C  [MSVCR110.dll+0x243dc]
C  [MSVCR110.dll+0x16629]
C  [MSVCR110.dll+0x6a312]
C  [MSVCP110.dll+0x2e2d8]
C  [MSVCP110.dll+0x2e47e]
C  [log4cplus.dll+0x229b]  log4cplus::thread::SyncGuard<log4cplus::thread::Mutex>::SyncGuard<log4cplus::thread::Mutex>+0x2b
C  [log4cplus.dll+0x3f1dd]  log4cplus::spi::ObjectRegistryBase::clear+0x2d
C  [log4cplus.dll+0x14225]  log4cplus::`anonymous namespace'::DefaultContext::~DefaultContext+0x45
C  [log4cplus.dll+0x143a5]  log4cplus::`anonymous namespace'::destroy_default_context::~destroy_default_context+0x25
C  [log4cplus.dll+0x559cd]  log4cplus::`anonymous namespace'::`dynamic atexit destructor for 'destroy_default_context_''+0xd
C  [log4cplus.dll+0x4e002]  _CRT_INIT+0xc1
C  [log4cplus.dll+0x4e228]  __DllMainCRTStartup+0xcf
C  [log4cplus.dll+0x4e152]  _DllMainCRTStartup+0x1c
~~~


---

Sent from sourceforge.net because log...@li... is subscribed to https://sourceforge.net/p/log4cplus/bugs/

To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/log4cplus/admin/bugs/options.  Or, if this is a mailing list, you can unsubscribe from the mailing list.

[Log4cplus-devel] [log4cplus:bugs] #343 Crash on app exit

[Ralf S. <ral...@us...>]

Tried it with log4cplus-1.2.1-rc1
Same result. But small difference in the call stack.

I've also attached the MSVC Debugger with log4cplus symbols and got:
> First-chance exception at 0x7560A9F2 in javaw.exe: Microsoft C++ exception: Concurrency::scheduler_resource_allocation_error at memory location 0x46BFEF34.
> Ausnahme (erste Chance) bei 0x58E2591B (jvm.dll) in javaw.exe: 0xC0000005: Zugriffsverletzung beim Lesen an Position 0x00000010
> 


Attachments:

- [hs_err_pid6884.log](https://sourceforge.net/p/log4cplus/bugs/_discuss/thread/4d9f53d7/c87b/attachment/hs_err_pid6884.log) (27.8 kB; application/octet-stream)


---

** [bugs:#343] Crash on app exit**

**Status:** open
**Group:** v1.2.0
**Labels:** java v1.2.0 
**Created:** Fri Jun 23, 2017 03:02 PM UTC by Ralf Sieger
**Last Updated:** Mon Jul 10, 2017 05:19 AM UTC
**Owner:** Václav Haisman
**Attachments:**

- [log4cplus_debug_hs_err_pid11184.log](https://sourceforge.net/p/log4cplus/bugs/343/attachment/log4cplus_debug_hs_err_pid11184.log) (23.5 kB; application/octet-stream)
- [log4cplus_release_hs_err_pid10836.log](https://sourceforge.net/p/log4cplus/bugs/343/attachment/log4cplus_release_hs_err_pid10836.log) (23.9 kB; application/octet-stream)


log4cplus:
- 1.2.0
- Visual Studio 2012
- config: release and debug
- windows 10, i7 4770

client:
- 32 bit Java 7 application
- log4cplus as dll
- log4cplus.lib and log4cplusD.lib
- multibyte chars
- see attached logfiles
- client DLL compile settings: no MFC, no ATL, multibyte charset, /MDd and /MD

We use log4cplus in an custom C++ dll which itself gets dynamically loaded in java program.
during the runtime everything works ok.
At application exit we see an java hotspot error (see logs). 
This happens with and without calling log4cplus::Logger::shutdown();
The problem also occurs if nothing but log4cplus::initialize(); and log4cplus::Logger::shutdown(); are called.

From the hotspot error it looks like an cleanup issue:
~~~
Stack: [0x46760000,0x467b0000],  sp=0x467aee5c,  free space=315k
Native frames: (J=compiled Java code, j=interpreted, Vv=VM code, C=native code)
C  [ntdll.dll+0xecc94]
C  [ntdll.dll+0x9683a]
C  [KERNEL32.DLL+0x1dbb9]
C  [MSVCR110.dll+0x9fa77]
C  [MSVCR110.dll+0x4defc]
C  [MSVCR110.dll+0x4f4cf]
C  [MSVCR110.dll+0x2431b]
C  [MSVCR110.dll+0x243dc]
C  [MSVCR110.dll+0x16629]
C  [MSVCR110.dll+0x6a312]
C  [MSVCP110.dll+0x2e2d8]
C  [MSVCP110.dll+0x2e47e]
C  [log4cplus.dll+0x229b]  log4cplus::thread::SyncGuard<log4cplus::thread::Mutex>::SyncGuard<log4cplus::thread::Mutex>+0x2b
C  [log4cplus.dll+0x3f1dd]  log4cplus::spi::ObjectRegistryBase::clear+0x2d
C  [log4cplus.dll+0x14225]  log4cplus::`anonymous namespace'::DefaultContext::~DefaultContext+0x45
C  [log4cplus.dll+0x143a5]  log4cplus::`anonymous namespace'::destroy_default_context::~destroy_default_context+0x25
C  [log4cplus.dll+0x559cd]  log4cplus::`anonymous namespace'::`dynamic atexit destructor for 'destroy_default_context_''+0xd
C  [log4cplus.dll+0x4e002]  _CRT_INIT+0xc1
C  [log4cplus.dll+0x4e228]  __DllMainCRTStartup+0xcf
C  [log4cplus.dll+0x4e152]  _DllMainCRTStartup+0x1c
~~~


---

Sent from sourceforge.net because log...@li... is subscribed to https://sourceforge.net/p/log4cplus/bugs/

To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/log4cplus/admin/bugs/options.  Or, if this is a mailing list, you can unsubscribe from the mailing list.

[Log4cplus-devel] [log4cplus:bugs] #343 Crash on app exit

[Václav H. <wi...@us...>]

I am not sure what to think about this. Could you please try HEAD of 1.2.x branch or 2.0.x branch? There have been some initialization and shutdown related changes since the 1.2.0 release. If just using newer log4cplus does not help, could you please try and run your app/java under a debugger with Microsoft symbols path set up so that we can see more of the contex, if at all possible?


---

** [bugs:#343] Crash on app exit**

**Status:** open
**Group:** v1.2.0
**Labels:** java v1.2.0 
**Created:** Fri Jun 23, 2017 03:02 PM UTC by Ralf Sieger
**Last Updated:** Mon Jul 10, 2017 05:04 AM UTC
**Owner:** Václav Haisman
**Attachments:**

- [log4cplus_debug_hs_err_pid11184.log](https://sourceforge.net/p/log4cplus/bugs/343/attachment/log4cplus_debug_hs_err_pid11184.log) (23.5 kB; application/octet-stream)
- [log4cplus_release_hs_err_pid10836.log](https://sourceforge.net/p/log4cplus/bugs/343/attachment/log4cplus_release_hs_err_pid10836.log) (23.9 kB; application/octet-stream)


log4cplus:
- 1.2.0
- Visual Studio 2012
- config: release and debug
- windows 10, i7 4770

client:
- 32 bit Java 7 application
- log4cplus as dll
- log4cplus.lib and log4cplusD.lib
- multibyte chars
- see attached logfiles
- client DLL compile settings: no MFC, no ATL, multibyte charset, /MDd and /MD

We use log4cplus in an custom C++ dll which itself gets dynamically loaded in java program.
during the runtime everything works ok.
At application exit we see an java hotspot error (see logs). 
This happens with and without calling log4cplus::Logger::shutdown();
The problem also occurs if nothing but log4cplus::initialize(); and log4cplus::Logger::shutdown(); are called.

From the hotspot error it looks like an cleanup issue:
~~~
Stack: [0x46760000,0x467b0000],  sp=0x467aee5c,  free space=315k
Native frames: (J=compiled Java code, j=interpreted, Vv=VM code, C=native code)
C  [ntdll.dll+0xecc94]
C  [ntdll.dll+0x9683a]
C  [KERNEL32.DLL+0x1dbb9]
C  [MSVCR110.dll+0x9fa77]
C  [MSVCR110.dll+0x4defc]
C  [MSVCR110.dll+0x4f4cf]
C  [MSVCR110.dll+0x2431b]
C  [MSVCR110.dll+0x243dc]
C  [MSVCR110.dll+0x16629]
C  [MSVCR110.dll+0x6a312]
C  [MSVCP110.dll+0x2e2d8]
C  [MSVCP110.dll+0x2e47e]
C  [log4cplus.dll+0x229b]  log4cplus::thread::SyncGuard<log4cplus::thread::Mutex>::SyncGuard<log4cplus::thread::Mutex>+0x2b
C  [log4cplus.dll+0x3f1dd]  log4cplus::spi::ObjectRegistryBase::clear+0x2d
C  [log4cplus.dll+0x14225]  log4cplus::`anonymous namespace'::DefaultContext::~DefaultContext+0x45
C  [log4cplus.dll+0x143a5]  log4cplus::`anonymous namespace'::destroy_default_context::~destroy_default_context+0x25
C  [log4cplus.dll+0x559cd]  log4cplus::`anonymous namespace'::`dynamic atexit destructor for 'destroy_default_context_''+0xd
C  [log4cplus.dll+0x4e002]  _CRT_INIT+0xc1
C  [log4cplus.dll+0x4e228]  __DllMainCRTStartup+0xcf
C  [log4cplus.dll+0x4e152]  _DllMainCRTStartup+0x1c
~~~


---

Sent from sourceforge.net because log...@li... is subscribed to https://sourceforge.net/p/log4cplus/bugs/

To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/log4cplus/admin/bugs/options.  Or, if this is a mailing list, you can unsubscribe from the mailing list.

[Log4cplus-devel] [log4cplus:bugs] #343 Crash on app exit

[Václav H. <wi...@us...>]

- **labels**: java --> java, v1.2.0



---

** [bugs:#343] Crash on app exit**

**Status:** open
**Group:** v1.2.0
**Labels:** java v1.2.0 
**Created:** Fri Jun 23, 2017 03:02 PM UTC by Ralf Sieger
**Last Updated:** Mon Jul 10, 2017 05:03 AM UTC
**Owner:** Václav Haisman
**Attachments:**

- [log4cplus_debug_hs_err_pid11184.log](https://sourceforge.net/p/log4cplus/bugs/343/attachment/log4cplus_debug_hs_err_pid11184.log) (23.5 kB; application/octet-stream)
- [log4cplus_release_hs_err_pid10836.log](https://sourceforge.net/p/log4cplus/bugs/343/attachment/log4cplus_release_hs_err_pid10836.log) (23.9 kB; application/octet-stream)


log4cplus:
- 1.2.0
- Visual Studio 2012
- config: release and debug
- windows 10, i7 4770

client:
- 32 bit Java 7 application
- log4cplus as dll
- log4cplus.lib and log4cplusD.lib
- multibyte chars
- see attached logfiles
- client DLL compile settings: no MFC, no ATL, multibyte charset, /MDd and /MD

We use log4cplus in an custom C++ dll which itself gets dynamically loaded in java program.
during the runtime everything works ok.
At application exit we see an java hotspot error (see logs). 
This happens with and without calling log4cplus::Logger::shutdown();
The problem also occurs if nothing but log4cplus::initialize(); and log4cplus::Logger::shutdown(); are called.

From the hotspot error it looks like an cleanup issue:
~~~
Stack: [0x46760000,0x467b0000],  sp=0x467aee5c,  free space=315k
Native frames: (J=compiled Java code, j=interpreted, Vv=VM code, C=native code)
C  [ntdll.dll+0xecc94]
C  [ntdll.dll+0x9683a]
C  [KERNEL32.DLL+0x1dbb9]
C  [MSVCR110.dll+0x9fa77]
C  [MSVCR110.dll+0x4defc]
C  [MSVCR110.dll+0x4f4cf]
C  [MSVCR110.dll+0x2431b]
C  [MSVCR110.dll+0x243dc]
C  [MSVCR110.dll+0x16629]
C  [MSVCR110.dll+0x6a312]
C  [MSVCP110.dll+0x2e2d8]
C  [MSVCP110.dll+0x2e47e]
C  [log4cplus.dll+0x229b]  log4cplus::thread::SyncGuard<log4cplus::thread::Mutex>::SyncGuard<log4cplus::thread::Mutex>+0x2b
C  [log4cplus.dll+0x3f1dd]  log4cplus::spi::ObjectRegistryBase::clear+0x2d
C  [log4cplus.dll+0x14225]  log4cplus::`anonymous namespace'::DefaultContext::~DefaultContext+0x45
C  [log4cplus.dll+0x143a5]  log4cplus::`anonymous namespace'::destroy_default_context::~destroy_default_context+0x25
C  [log4cplus.dll+0x559cd]  log4cplus::`anonymous namespace'::`dynamic atexit destructor for 'destroy_default_context_''+0xd
C  [log4cplus.dll+0x4e002]  _CRT_INIT+0xc1
C  [log4cplus.dll+0x4e228]  __DllMainCRTStartup+0xcf
C  [log4cplus.dll+0x4e152]  _DllMainCRTStartup+0x1c
~~~


---

Sent from sourceforge.net because log...@li... is subscribed to https://sourceforge.net/p/log4cplus/bugs/

To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/log4cplus/admin/bugs/options.  Or, if this is a mailing list, you can unsubscribe from the mailing list.

[Log4cplus-devel] [log4cplus:bugs] #343 Crash on app exit

[Václav H. <wi...@us...>]

- **labels**:  --> java
- **assigned_to**: Václav Haisman



---

** [bugs:#343] Crash on app exit**

**Status:** open
**Group:** v1.2.0
**Labels:** java 
**Created:** Fri Jun 23, 2017 03:02 PM UTC by Ralf Sieger
**Last Updated:** Fri Jun 23, 2017 03:02 PM UTC
**Owner:** Václav Haisman
**Attachments:**

- [log4cplus_debug_hs_err_pid11184.log](https://sourceforge.net/p/log4cplus/bugs/343/attachment/log4cplus_debug_hs_err_pid11184.log) (23.5 kB; application/octet-stream)
- [log4cplus_release_hs_err_pid10836.log](https://sourceforge.net/p/log4cplus/bugs/343/attachment/log4cplus_release_hs_err_pid10836.log) (23.9 kB; application/octet-stream)


log4cplus:
- 1.2.0
- Visual Studio 2012
- config: release and debug
- windows 10, i7 4770

client:
- 32 bit Java 7 application
- log4cplus as dll
- log4cplus.lib and log4cplusD.lib
- multibyte chars
- see attached logfiles
- client DLL compile settings: no MFC, no ATL, multibyte charset, /MDd and /MD

We use log4cplus in an custom C++ dll which itself gets dynamically loaded in java program.
during the runtime everything works ok.
At application exit we see an java hotspot error (see logs). 
This happens with and without calling log4cplus::Logger::shutdown();
The problem also occurs if nothing but log4cplus::initialize(); and log4cplus::Logger::shutdown(); are called.

From the hotspot error it looks like an cleanup issue:
~~~
Stack: [0x46760000,0x467b0000],  sp=0x467aee5c,  free space=315k
Native frames: (J=compiled Java code, j=interpreted, Vv=VM code, C=native code)
C  [ntdll.dll+0xecc94]
C  [ntdll.dll+0x9683a]
C  [KERNEL32.DLL+0x1dbb9]
C  [MSVCR110.dll+0x9fa77]
C  [MSVCR110.dll+0x4defc]
C  [MSVCR110.dll+0x4f4cf]
C  [MSVCR110.dll+0x2431b]
C  [MSVCR110.dll+0x243dc]
C  [MSVCR110.dll+0x16629]
C  [MSVCR110.dll+0x6a312]
C  [MSVCP110.dll+0x2e2d8]
C  [MSVCP110.dll+0x2e47e]
C  [log4cplus.dll+0x229b]  log4cplus::thread::SyncGuard<log4cplus::thread::Mutex>::SyncGuard<log4cplus::thread::Mutex>+0x2b
C  [log4cplus.dll+0x3f1dd]  log4cplus::spi::ObjectRegistryBase::clear+0x2d
C  [log4cplus.dll+0x14225]  log4cplus::`anonymous namespace'::DefaultContext::~DefaultContext+0x45
C  [log4cplus.dll+0x143a5]  log4cplus::`anonymous namespace'::destroy_default_context::~destroy_default_context+0x25
C  [log4cplus.dll+0x559cd]  log4cplus::`anonymous namespace'::`dynamic atexit destructor for 'destroy_default_context_''+0xd
C  [log4cplus.dll+0x4e002]  _CRT_INIT+0xc1
C  [log4cplus.dll+0x4e228]  __DllMainCRTStartup+0xcf
C  [log4cplus.dll+0x4e152]  _DllMainCRTStartup+0x1c
~~~


---

Sent from sourceforge.net because log...@li... is subscribed to https://sourceforge.net/p/log4cplus/bugs/

To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/log4cplus/admin/bugs/options.  Or, if this is a mailing list, you can unsubscribe from the mailing list.

[Log4cplus-devel] log4cplus 2.0.0-RC2 released [take 2]

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

  *

    Avoid copying whole message just to prepend message length in
    |SocketAppender|. Instead, use OS specific “gather” socket write.

  *

    Fixed GitHub issue #136
    <https://github.com/log4cplus/log4cplus/issues/136>.

  *

    |FileAppender| classes now have |TextMode| property that can be set
    to |Binary| or |Text| (default) to specify underlying IO stream
    behavior with respect to end-of-line handling. (Patch by
    raphaelmarcucci).

  *

    Fixed compilation issues when building log4cplus with Visual Studio
    and Clang toolchain.

  *

    Fixed various shutdown and initialization related deadlocks and
    crashes. GitHub issues #251
    <https://github.com/log4cplus/log4cplus/issues/251>, #253
    <https://github.com/log4cplus/log4cplus/issues/253>.

  *

    Fixed GitHub issue #243
    <https://github.com/log4cplus/log4cplus/issues/243>. Single-threaded
    build with Visual Studio and CMake were not single-threaded.

  *

    Fixed GitHub issue #250
    <https://github.com/log4cplus/log4cplus/issues/250>. Creating WiX
    based installer using CPack does not work because of missing license
    file.

​

-- 
VH

[Log4cplus-devel] log4cplus 2.0.0-RC2 released

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

I have released log4cplus 2.0.0-RC2
<https://sourceforge.net/projects/log4cplus/files/log4cplus-stable/2.0.0/>:

  *

    Avoid copying whole message just to prepend message length in
    |SocketAppender|. Instead, use OS specific “gather” socket write.

  *

    Fixed GitHub issue #136
    <https://github.com/log4cplus/log4cplus/issues/136>.

  *

    |FileAppender| classes now have |TextMode| property that can be set
    to |Binary| or |Text| (default) to specify underlying IO stream
    behavior with respect to end-of-line handling. (Patch by
    raphaelmarcucci).

  *

    Fixed compilation issues when building log4cplus with Visual Studio
    and Clang toolchain.

  *

    Fixed various shutdown and initialization related deadlocks and
    crashes. GitHub issues #251
    <https://github.com/log4cplus/log4cplus/issues/251>, #253
    <https://github.com/log4cplus/log4cplus/issues/253>.

  *

    Fixed GitHub issue #243
    <https://github.com/log4cplus/log4cplus/issues/243>. Single-threaded
    build with Visual Studio and CMake were not single-threaded.

  *

    Fixed GitHub issue #250
    <https://github.com/log4cplus/log4cplus/issues/250>. Creating WiX
    based installer using CPack does not work because of missing license
    file.

​

-- 
VH

[Log4cplus-devel] [log4cplus:bugs] #343 Crash on app exit

[Ralf S. <ral...@us...>]

---

** [bugs:#343] Crash on app exit**

**Status:** open
**Group:** v1.2.0
**Created:** Fri Jun 23, 2017 03:02 PM UTC by Ralf Sieger
**Last Updated:** Fri Jun 23, 2017 03:02 PM UTC
**Owner:** nobody
**Attachments:**

- [log4cplus_debug_hs_err_pid11184.log](https://sourceforge.net/p/log4cplus/bugs/343/attachment/log4cplus_debug_hs_err_pid11184.log) (23.5 kB; application/octet-stream)
- [log4cplus_release_hs_err_pid10836.log](https://sourceforge.net/p/log4cplus/bugs/343/attachment/log4cplus_release_hs_err_pid10836.log) (23.9 kB; application/octet-stream)


log4cplus:
- 1.2.0
- Visual Studio 2012
- config: release and debug
- windows 10, i7 4770

client:
- 32 bit Java 7 application
- log4cplus as dll
- log4cplus.lib and log4cplusD.lib
- multibyte chars
- see attached logfiles
- client DLL compile settings: no MFC, no ATL, multibyte charset, /MDd and /MD

We use log4cplus in an custom C++ dll which itself gets dynamically loaded in java program.
during the runtime everything works ok.
At application exit we see an java hotspot error (see logs). 
This happens with and without calling log4cplus::Logger::shutdown();
The problem also occurs if nothing but log4cplus::initialize(); and log4cplus::Logger::shutdown(); are called.

>From the hotspot error it looks like an cleanup issue:
~~~
Stack: [0x46760000,0x467b0000],  sp=0x467aee5c,  free space=315k
Native frames: (J=compiled Java code, j=interpreted, Vv=VM code, C=native code)
C  [ntdll.dll+0xecc94]
C  [ntdll.dll+0x9683a]
C  [KERNEL32.DLL+0x1dbb9]
C  [MSVCR110.dll+0x9fa77]
C  [MSVCR110.dll+0x4defc]
C  [MSVCR110.dll+0x4f4cf]
C  [MSVCR110.dll+0x2431b]
C  [MSVCR110.dll+0x243dc]
C  [MSVCR110.dll+0x16629]
C  [MSVCR110.dll+0x6a312]
C  [MSVCP110.dll+0x2e2d8]
C  [MSVCP110.dll+0x2e47e]
C  [log4cplus.dll+0x229b]  log4cplus::thread::SyncGuard<log4cplus::thread::Mutex>::SyncGuard<log4cplus::thread::Mutex>+0x2b
C  [log4cplus.dll+0x3f1dd]  log4cplus::spi::ObjectRegistryBase::clear+0x2d
C  [log4cplus.dll+0x14225]  log4cplus::`anonymous namespace'::DefaultContext::~DefaultContext+0x45
C  [log4cplus.dll+0x143a5]  log4cplus::`anonymous namespace'::destroy_default_context::~destroy_default_context+0x25
C  [log4cplus.dll+0x559cd]  log4cplus::`anonymous namespace'::`dynamic atexit destructor for 'destroy_default_context_''+0xd
C  [log4cplus.dll+0x4e002]  _CRT_INIT+0xc1
C  [log4cplus.dll+0x4e228]  __DllMainCRTStartup+0xcf
C  [log4cplus.dll+0x4e152]  _DllMainCRTStartup+0x1c
~~~


---

Sent from sourceforge.net because log...@li... is subscribed to https://sourceforge.net/p/log4cplus/bugs/

To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/log4cplus/admin/bugs/options.  Or, if this is a mailing list, you can unsubscribe from the mailing list.