user29691: Where can I check the output logs generated from LogPrint() statements in the bitcoind source code.
PS: Please do not confuse this with the LogPrintf() statement, which logs the output into debug.log file.

user3697: LogPrint and LogPrintf are very similar.
Mind the definiton: #define LogPrintf(...) LogPrint(NULL, __VA_ARGS__)
LogPrint's will only end up in your debug.log when enabling the corresponding category. Enabling works over the -debug arg.
-debug=mempool,net would output all LogPrint("mempool",...) or LogPrint("net",...) to the debug log, or to stdout if -printtoconsole has been enabled.

29691: <p>Where can I check the output logs generated from <code>LogPrint()</code> statements in the <code>bitcoind</code> source code.</p>

<p>PS: Please do not confuse this with the <code>LogPrintf()</code> statement, which logs the output into <code>debug.log</code> file.</p>
 3697: <p><code>LogPrint</code> and <code>LogPrintf</code> are very similar.</p>

<p>Mind the definiton: <code>#define LogPrintf(...) LogPrint(NULL, __VA_ARGS__)</code></p>

<p><code>LogPrint</code>'s will only end up in your <code>debug.log</code> when enabling the corresponding category. Enabling works over the <code>-debug</code> arg.</p>

<p><code>-debug=mempool,net</code> would output all <code>LogPrint("mempool",...)</code> or <code>LogPrint("net",...)</code> to the debug log, or to stdout if <code>-printtoconsole</code> has been enabled.</p>
