[
https://issues.apache.org/jira/browse/DRILL-5441?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15973492#comment-15973492
]
Rob Wu commented on DRILL-5441:
-------------------------------
With Log turned off:
<?xml version="1.0"?>
-<valgrindoutput>
<protocolversion>4</protocolversion>
<protocoltool>memcheck</protocoltool>
-<preamble>
<line>Memcheck, a memory error detector</line>
<line>Copyright (C) 2002-2012, and GNU GPL'd, by Julian Seward et al.</line>
<line>Using Valgrind-3.8.1 and LibVEX; rerun with -h for copyright info</line>
<line>Command: /opt/io/64/bin/iodbctestw DSN=MapR Drill 64-bit</line>
</preamble>
<pid>32428</pid>
<ppid>14305</ppid>
<tool>memcheck</tool>
-<args>
-<vargv>
<exe>/usr/bin/valgrind</exe>
<arg>--leak-check=yes</arg>
<arg>--xml=yes</arg>
<arg>--xml-file=/media/110valgrind-1371028 LOG OFF.xml</arg>
</vargv>
-<argv>
<exe>/opt/io/64/bin/iodbctestw</exe>
<arg>DSN=MapR Drill 64-bit</arg>
</argv>
</args>
-<status>
<state>RUNNING</state>
<time>00:00:00:00.050 </time>
</status>
-<status>
<state>FINISHED</state>
<time>00:00:00:13.119 </time>
</status>
</valgrindoutput>
> Drill Client: Invalid read error when logger is turned on
> ---------------------------------------------------------
>
> Key: DRILL-5441
> URL: https://issues.apache.org/jira/browse/DRILL-5441
> Project: Apache Drill
> Issue Type: Bug
> Components: Client - C++
> Affects Versions: 1.10.0
> Reporter: Rob Wu
> Priority: Minor
>
> The memory access issue only occurs when the log level for the drill client
> is set to DEBUG or above. By turning off or down the log level, the issue is
> no longer observed.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
