CODEWITHSUNDEEP
linuxvalgrind
Igor
Igor

Reputation: 6245

Valgrind does not send the output to the file

ALL,

igor@IgorReinCloud ~/dbhandler/Debug/dbhandler $ valgrind --demangle=yes dbhandler --log-file=memcheck.log --leak-check=full
==28275== Memcheck, a memory error detector
==28275== Copyright (C) 2002-2017, and GNU GPL'd, by Julian Seward et al.
==28275== Using Valgrind-3.13.0 and LibVEX; rerun with -h for copyright info
==28275== Command: dbhandler --log-file=memcheck.log --leak-check=full

// Some errors logged on screen

Unknown long option 'log-file'

// Some more errors logged on screen

Usage: dbhandler [-h] [--verbose]
  -h, --help    show this help message
  --verbose     generate verbose log messages
==28275==
==28275== HEAP SUMMARY:
==28275==     in use at exit: 1,549,966 bytes in 16,372 blocks
==28275==   total heap usage: 177,899 allocs, 161,527 frees,
10,849,729 bytes allocated
==28275==
==28275== LEAK SUMMARY:
==28275==    definitely lost: 0 bytes in 0 blocks
==28275==    indirectly lost: 0 bytes in 0 blocks
==28275==      possibly lost: 3,408 bytes in 32 blocks
==28275==    still reachable: 1,464,270 bytes in 15,670 blocks
==28275==                       of which reachable via heuristic:
==28275==                         length64           : 4,872 bytes in 81 blocks
==28275==                         newarray           : 2,096 bytes in 51 blocks
==28275==         suppressed: 0 bytes in 0 blocks
==28275== Rerun with --leak-check=full to see details of leaked memory
==28275==
==28275== For counts of detected and suppressed errors, rerun with: -v
==28275== Use --track-origins=yes to see where uninitialised values come from
==28275== ERROR SUMMARY: 28 errors from 8 contexts (suppressed: 0 from 0)

However,

igor@IgorReinCloud ~/dbhandler/Debug/dbhandler $ valgrind --help | grep log
    --time-stamp=no|yes       add timestamps to log messages? [no]
    --log-fd=<number>         log messages to file descriptor [2=stderr]
    --log-file=<file>         log messages to <file>
    --log-socket=ipaddr:port  log messages to socket ipaddr:port
igor@IgorReinCloud ~/dbhandler/Debug/dbhandler $

So what the problem is? Why the messages are not going to the log file as it should? Am I missing an option here?

TIA!

Upvotes: 1

Views: 2219

Answers (1)

Jonathan Leffler
Jonathan Leffler

Reputation: 753425

Put the options to Valgrind before the program you want it to check. It assumes options after the program name are options to the program, not Valgrind.

Hence, you have:

valgrind --demangle=yes dbhandler --log-file=memcheck.log --leak-check=full

but you should be using:

valgrind --demangle=yes --log-file=memcheck.log --leak-check=full dbhandler

or even use -- to state that you've finished the options to Valgrind:

valgrind --demangle=yes --log-file=memcheck.log --leak-check=full -- dbhandler

The Unknown long option log-file message probably comes from dbhandler and not Valgrind. It's also why you're getting the 'usage' message from dbhandler.

Upvotes: 1

Related Questions