Fix: Avoid potential null dereference with log4j loggers
authorAlexandre Montplaisir <alexmonthy@efficios.com>
Thu, 19 May 2016 18:49:06 +0000 (14:49 -0400)
committerMathieu Desnoyers <mathieu.desnoyers@efficios.com>
Thu, 19 May 2016 19:50:52 +0000 (15:50 -0400)
commit2b218c9aeb9face9c713c51e7169539deb1b263d
tree9191ad41d30bf4f8db4fd372110de630c8fa5179
parent22191ffd5680d377e6f92f783c9b2302708732ab
Fix: Avoid potential null dereference with log4j loggers

Coverity warns that the return of LogManager.getCurrentLoggers()
can contain null elements. Add an explicit null check to skip those.

Signed-off-by: Alexandre Montplaisir <alexmonthy@efficios.com>
Signed-off-by: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
liblttng-ust-java-agent/java/lttng-ust-agent-log4j/org/lttng/ust/agent/log4j/LttngLog4jAgent.java
This page took 0.024914 seconds and 4 git commands to generate.