From: "Sebastian H." <vand2@gmx.de>
To: Clemens Ladisch <clemens@ladisch.de>
Cc: ALSA Development Mailing List <alsa-devel@alsa-project.org>
Subject: Re: alsa-lib TLVs and valgrind
Date: Wed, 02 Feb 2011 14:18:35 +0100 [thread overview]
Message-ID: <4D4959AB.1050703@gmx.de> (raw)
In-Reply-To: <4D495859.6070101@ladisch.de>
Am 02.02.2011 14:12, schrieb Clemens Ladisch:
> Sebastian H. wrote:
>> I'm about to release a new version of alsamixer-qt4
>> (now named qasmixer) and ran the program through valgrind.
>>
>> valgrind --track-origins=yes src/qasmixer &> valgrind.log
>>
>> The log file contains tons of warnings like this
>>
>> ==3432== Conditional jump or move depends on uninitialised value(s)
>> ...
>> ... (qasmixer function calls)
>> ...
>> ==3432== Uninitialised value was created by a heap allocation
>> ... malloc (vg_replace_malloc.c:236)
>> ... init_db_range (simple_none.c:1111)
>> ... get_dB_range (simple_none.c:1156)
>> ... get_dB_range_ops (simple_none.c:1173)
>> ... snd_mixer_selem_get_playback_dB_range (simple.c:298)
>
> Valgrind doesn't know about some of the ALSA ioctls.
> Somebody would have to add them to valgrind.
That seems to require quite some effort - also to maintain.
Couldn't just the dB min/max values be initialized with 0 or sth.?
Sebastian
next prev parent reply other threads:[~2011-02-02 13:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-02 11:54 alsa-lib TLVs and valgrind Sebastian H.
2011-02-02 13:12 ` Clemens Ladisch
2011-02-02 13:18 ` Sebastian H. [this message]
2011-02-02 15:12 ` Clemens Ladisch
2011-02-02 15:16 ` Sebastian H.
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4D4959AB.1050703@gmx.de \
--to=vand2@gmx.de \
--cc=alsa-devel@alsa-project.org \
--cc=clemens@ladisch.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).