I don't know how the loader works on OSX, but that seems somewhat
unlikely to me - either it should be complaining that the APR library
doesn't exist, or something related to APR should be in the stack
trace.
Unfortunately at this moment I'm just guessing wildly as to what the
issue may be.
The example applications (at least trivial and console) run fine so dynamic
loading alone is not an issue (there are no static libs built). I do see
that we only reference the liblog4cxx library in our makefile while the
examples also reference the apr / apu libraries. Perhaps we need to tweak
As far as I'm aware, the unit tests do use the dynamic library.
Looking at the stacktrace, I would expect the '--version' argument to
not work, since it seems to be happening before main() - my suspicion
is that your code has another static initialization(unrelated to
log4cxx) someplace, that is
Hey Robert,
I agree that the socket issue is most likely unrelated. I'll try to look
at this.
I just noticed that our application supports '--version' which simply
prints the version and exits. Even using this results in the same segfault
so it seems the issue is more related to dynamic
Update: I've added a 2.0.13 RC2 release at GitHub with the suggested
modifications to release artifacts (source and binary zips). The released
functionality remains unchanged.
-d
On 2021/10/28 08:49:23, Davyd McColl wrote:
Hi Robert
Thanks for checking all these things and feeding back to me
Hi Robert
Thanks for checking all these things and feeding back to me
1. SDK reference: I've linked in the older reference now, since the sdk hasn't
changed, but this reminds me that I wanted to add building this to the release
pipeline, and hadn't yet found a good generator - I'll put this on
