July 14, 2011

valgrind doesn't start `ags`

Hi, I started `valgrind` to debug my application, because it showed me the following output:

ags_devout_play_functions: start
remove: AgsVolumeAudioSignal
remove: AgsVolumeRecycling
remove: AgsVolumeChannel
remove: AgsStreamAudioSignal
remove: AgsStreamRecycling
remove: AgsStreamChannelRun
remove: AgsPlayAudioSignal
remove: AgsPlayRecycling
AgsPlayRecycling: 9370c0
remove: AgsPlayRecycling
AgsPlayRecycling: 9370c0
remove: AgsPlayRecycling
AgsPlayRecycling: 9370c0
remove: AgsPlayChannelRun

AgsPlayRecycling has always the same address but it can't be removed several times, because it was allocated and added only once. But the output shows me something else. So I wanted to start `valgrind`, but I just get the following output:

joel@debian:~/workspace/ags$ valgrind /home/joel/workspace/ags/ags
==4446== Memcheck, a memory error detector
==4446== Copyright (C) 2002-2010, and GNU GPL'd, by Julian Seward et al.
==4446== Using Valgrind-3.7.0.SVN and LibVEX; rerun with -h for copyright info
==4446== Command: /home/joel/workspace/ags/ags
--4446-- Warning: DWARF2 CFI reader: unhandled DW_OP_ opcode 0x2a

valgrind: m_debuginfo/readdwarf.c:2397 (copy_convert_CfiExpr_tree): Assertion 'srcix >= 0 && srcix < VG_(sizeXA)(srcxa)' failed.
==4446== at 0x3802CFC6: ??? (in /usr/lib/valgrind/memcheck-amd64-linux)

sched status:

Note: see also the FAQ in the source distribution.
It contains workarounds to several common problems.
In particular, if Valgrind aborted or crashed after
identifying problems in your program, there's a good chance
that fixing those problems will prevent Valgrind aborting or
crashing, especially if it happened in m_mallocfree.c.

If that doesn't help, please report this bug to: www.valgrind.org

In the bug report, send all the above text, the valgrind
version, and what OS and version you are using. Thanks.

There is something corrupted, please help me.
I'm using debian unstable/experimental with a self compiled linux kernel (