Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Clemens Ladisch <clemens@ladisch.de>
To: Mathieu Monney <zittix_all@xwaves.net>
Cc: alsa-devel@alsa-project.org
Subject: Re: ioctl(arg) - uninitialised byte(s) in alsa lib
Date: Wed, 12 Mar 2008 13:15:43 +0100	[thread overview]
Message-ID: <47D7C96F.8010109@ladisch.de> (raw)
In-Reply-To: <47D7C358.6050401@xwaves.net>

Mathieu Monney wrote:
> I'm currently working on a small audio stack on top of alsa and I'm
> getting some "Syscall param ioctl(arg) contains uninitialized byte(s)"
> errors when I run my program using valgrind.
>
> ==14279==    by 0x40DE911: snd_pcm_prepare (in /usr/lib/libasound.so.2.0.0)

The ioctl call is in src/pcm/pcm_hw.c:

	if (ioctl(fd, SNDRV_PCM_IOCTL_PREPARE) < 0) {

Apparently, valgrind doesn't detect the cases where there is no third
argument.


Regards,
Clemens

      reply	other threads:[~2008-03-12 12:14 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-12 11:49 ioctl(arg) - uninitialised byte(s) in alsa lib Mathieu Monney
2008-03-12 12:15 ` Clemens Ladisch [this message]

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=47D7C96F.8010109@ladisch.de \
    --to=clemens@ladisch.de \
    --cc=alsa-devel@alsa-project.org \
    --cc=zittix_all@xwaves.net \
    /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