All of lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel Mack <daniel@caiaq.org>
To: alsa-devel@alsa-project.org
Subject: snd_pcm_hw_params_get_period_size points to __old_ symbol
Date: Sun, 22 Feb 2009 22:35:53 +0100	[thread overview]
Message-ID: <20090222213553.GA5893@buzzloop.caiaq.de> (raw)

Hi,

With alsa-lib and alsa-utils cross-compiled for ARM by
buildroot (currently version 1.0.19, but earlier versions
seem to be equally affected), I encounter the effect that
snd_pcm_hw_params_get_period_size() does not write the expected
value to the given snd_pcm_uframes_t pointer. In fact, this
variable is not written at all. This makes aplay calculate 0
for chunk_bytes in set_params() and then exit with the bogus error
message "Not enough memory". I did some tracing and found out that
the function called for snd_pcm_hw_params_get_period_size() is in
fact __old_snd_pcm_hw_params_get_period_size() which has a different
footprint and hence the pointer given to it is leaved untouched.

As I don't fully understand all the system behind the symbol names
remapping, I'm stuck here. Can anybody reproduce this bug?

Daniel

             reply	other threads:[~2009-02-22 21:35 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-22 21:35 Daniel Mack [this message]
2009-02-22 22:15 ` snd_pcm_hw_params_get_period_size points to __old_ symbol Liam Girdwood
2009-02-22 22:18   ` Daniel Mack
2009-02-22 22:22   ` Daniel Mack
2009-02-22 22:24     ` Liam Girdwood
2009-02-22 22:27       ` Daniel Mack
2009-02-22 22:32         ` Liam Girdwood
2009-02-23 11:52     ` Alan Horstmann
2009-02-23 11:32       ` Daniel Mack
2009-02-23 12:30         ` Alan Horstmann

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=20090222213553.GA5893@buzzloop.caiaq.de \
    --to=daniel@caiaq.org \
    --cc=alsa-devel@alsa-project.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.