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:52:20 +0000 (15:52 -0400)
commit187d89d3e7f80f79f50eea6f70f3a0a937aaf67e
tree7e2d9dfd925d8b3f3539555148d04356caaccddd
parent5c588ccfbdb647157a678ce4211e6563edb035e3
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.028967 seconds and 4 git commands to generate.