Re: [I] Produce single file (logging-log4net)

2025-07-15 Thread via GitHub
gdziadkiewicz commented on issue #263: URL: https://github.com/apache/logging-log4net/issues/263#issuecomment-3076717649 Hi, I can try. Can you upload the code and binaries for repro? -- This is an automated message from the Apache Git Service. To respond to the message, please log on to

Re: [PR] Prevent potential deadlock on shutdown when using AsyncAppender [logging-log4cxx]

2025-07-15 Thread via GitHub
swebb2066 commented on code in PR #511: URL: https://github.com/apache/logging-log4cxx/pull/511#discussion_r2209155149 ## src/examples/cpp/MyApp1.cpp: ## @@ -20,5 +20,6 @@ int main(int argc, char **argv) { LOG4CXX_INFO(logger, "Entering application."); foo();

Re: [PR] Prevent potential deadlock on shutdown when using AsyncAppender [logging-log4cxx]

2025-07-15 Thread via GitHub
swebb2066 commented on code in PR #511: URL: https://github.com/apache/logging-log4cxx/pull/511#discussion_r2209155149 ## src/examples/cpp/MyApp1.cpp: ## @@ -20,5 +20,6 @@ int main(int argc, char **argv) { LOG4CXX_INFO(logger, "Entering application."); foo();

Re: [PR] Prevent potential deadlock on shutdown when using AsyncAppender [logging-log4cxx]

2025-07-15 Thread via GitHub
swebb2066 commented on code in PR #511: URL: https://github.com/apache/logging-log4cxx/pull/511#discussion_r2209109613 ## src/examples/cpp/MyApp1.cpp: ## @@ -20,5 +20,6 @@ int main(int argc, char **argv) { LOG4CXX_INFO(logger, "Entering application."); foo();

Re: [PR] Prevent potential deadlock on shutdown when using AsyncAppender [logging-log4cxx]

2025-07-15 Thread via GitHub
swebb2066 commented on code in PR #511: URL: https://github.com/apache/logging-log4cxx/pull/511#discussion_r2209107114 ## src/examples/cpp/MyApp1.cpp: ## @@ -1,11 +1,11 @@ -#include +#include #include -static auto logger = log4cxx::Logger::getLogger("MyApp"); Review Comme

Re: [PR] Prevent potential deadlock on shutdown when using AsyncAppender [logging-log4cxx]

2025-07-15 Thread via GitHub
rm5248 commented on code in PR #511: URL: https://github.com/apache/logging-log4cxx/pull/511#discussion_r2209095595 ## src/examples/cpp/MyApp1.cpp: ## @@ -1,11 +1,11 @@ -#include +#include #include -static auto logger = log4cxx::Logger::getLogger("MyApp"); Review Comment:

[I] Produce single file (logging-log4net)

2025-07-15 Thread via GitHub
ringchenhao opened a new issue, #263: URL: https://github.com/apache/logging-log4net/issues/263 When publishing a C# application with .NET 8.0 framework, if the "Produce single file" option is enabled in the publish settings, testing the generated EXE reveals that neither the log folder nor

Re: [I] Short-lived macOS program with MultiprocessRollingFileAppender and AsyncAppender hangs upon exit with EXC_BAD_ACCESS in a worker thread [logging-log4cxx]

2025-07-15 Thread via GitHub
swebb2066 commented on issue #510: URL: https://github.com/apache/logging-log4cxx/issues/510#issuecomment-3076461698 Your application must call `LogManager::shutdown` when it exits to prevent undefined behaviour when using this appender. I have updated the documentation in #511 -

Re: [PR] Upgrade Jackson from 2.x to 3.0.0-rc5 [logging-log4j2]

2025-07-15 Thread via GitHub
kurtostfeld commented on PR #3701: URL: https://github.com/apache/logging-log4j2/pull/3701#issuecomment-3075170184 @ppkarwasz awesome. I suspected it was a flaky test. thank you. If there are issues with the Jackson 3.0 upgrade, I'd like to help investigate and resolve them. I use log4j on

[I] Badly formatted status msg in AbstractDriverManagerConnectionSource [logging-log4j2]

2025-07-15 Thread via GitHub
ppkarwasz opened a new issue, #3828: URL: https://github.com/apache/logging-log4j2/issues/3828 ### Discussed in https://github.com/apache/logging-log4j2/discussions/3827 Originally posted by **RichMacDonald** July 15, 2025 Version 2.24.3 org.apache.logging.log4j.core.ap

Re: [PR] Gradle: Add `buildSrc` to the sample project [logging-log4j-samples]

2025-07-15 Thread via GitHub
MartyIX commented on PR #350: URL: https://github.com/apache/logging-log4j-samples/pull/350#issuecomment-3074490645 That's great insight! I opened #351 which reports the error. I'm closing this PR. -- This is an automated message from the Apache Git Service. To respond to the mess

Re: [PR] Gradle: Add `buildSrc` to the sample project [logging-log4j-samples]

2025-07-15 Thread via GitHub
MartyIX closed pull request #350: Gradle: Add `buildSrc` to the sample project URL: https://github.com/apache/logging-log4j-samples/pull/350 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specif

[PR] Gradle: Repro for issue 3779 [logging-log4j-samples]

2025-07-15 Thread via GitHub
MartyIX opened a new pull request, #351: URL: https://github.com/apache/logging-log4j-samples/pull/351 This is a PR that addresses https://github.com/apache/logging-log4j-samples/pull/350#issuecomment-3069913098. Now, this command ``` export LOG4J_VERSION=2.25.1; ./gradlew :

[PR] Prevent potential deadlock on shutdown when using AsyncAppender [logging-log4cxx]

2025-07-15 Thread via GitHub
swebb2066 opened a new pull request, #511: URL: https://github.com/apache/logging-log4cxx/pull/511 When the application does not call LogManager::shutdown before program exit, the single LogLog instance is destroyed before AsynAppender terminates. Undefined behaviour (use-after-free) arises