[mythtv-users] finding leaks

[Eric Sharkey]

On Mon, Sep 1, 2014 at 10:29 PM, Michael T. Dean
<mtdean at thirdcontact.com> wrote:
> On 09/01/2014 01:43 PM, Eric Sharkey wrote:
>>
>> Valgrind is a powerful tool for catching leaks, but
>> it's meant for developers to use.  Generally, you only want to run it
>> on unstripped binaries, which means the first step is to compile
>> mythtv from sources.  You don't want to use a prepackaged deb/rpm.
>> These usually have the symbol table stripped prior to packaging.
>
>
> And placed in a separate package--so you just need to install that package.
> No need to compile from source

And *sometimes* placed in a separate package.  The packager may or may
not build a debug symbol package which may or may not be made
available to the end user.

For example, if you get your MythTV packages here:

http://www.deb-multimedia.org/dists/unstable/main/binary-amd64/

You can see some packages have symbol tables packages available:

176. libgegl-0.2-0 Generic Graphics Library.
177. libgegl-0.2-0-dbg Generic Graphics Library (debugging symbols).

But others do not:

229. libmyth-0.27-0 Common library code for MythTV and add-on modules (runtime)
230. libmyth-dev Common library code for MythTV and add-on modules (development)
231. libmythavcodec54 libavcodec package for MythTV

In which case you must compile from source if you want the symbols.
(Or pester the packager to create a symbols package.)

Eric