All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Clemens Ladisch" <cladisch@fastmail.net>
To: "Pharaoh ." <pharaoh137@gmail.com>
Cc: alsa-devel@alsa-project.org
Subject: Re: pcm->private_data is NULL in alsa core!!
Date: Tue, 19 Jun 2007 16:29:38 +0200	[thread overview]
Message-ID: <1182263378.1273.1195944481@webmail.messagingengine.com> (raw)
In-Reply-To: <61445c750706190430i7d8f37b3g95326d7aee6c5056@mail.gmail.com>

Pharaoh . wrote:
> in register codec 4 pvt data is c3d81180
> Registering the sound card
> in register codec 5 pvt data is c3998f20
> 
> i.e. after registering the sound card the value changes/gets
> corrupted, and c3998f20
> is not the value I get everytime, so I am thinking it is corrrupted somehow.

I'd guess the memory gets overwritten.

> But back in probe, after above function are executed, i.e. after
> register codec is over, I get the correct value for
> eac->pcm->private_data i.e. c3d81180, but by now the value of
> pcm->private_data is corrupted!

This implies that eac->pcm != pcm.

It seems quite a lot of memory gets corrupted.
Try to check which one of the various "eac" and "pcm" pointers changes
its value.


HTH
Clemens

  parent reply	other threads:[~2007-06-19 14:29 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-16 12:50 pcm->private_data is NULL in alsa core!! Pharaoh .
2007-06-17 15:45 ` Pharaoh .
2007-06-18  7:37 ` Clemens Ladisch
2007-06-18 11:56   ` Pharaoh .
2007-06-18 11:58     ` Pharaoh .
2007-06-19 11:10     ` Clemens Ladisch
2007-06-19 11:30       ` Pharaoh .
2007-06-19 12:17         ` Pharaoh .
2007-06-19 14:29         ` Clemens Ladisch [this message]
2007-06-20 10:18           ` Pharaoh .
2007-06-20 11:12             ` Pharaoh .
2007-06-20 11:16               ` Pharaoh .
2007-06-20 16:13                 ` Clemens Ladisch
2007-06-20 16:29                   ` Pharaoh .
2007-06-22 20:03                     ` Pharaoh .

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=1182263378.1273.1195944481@webmail.messagingengine.com \
    --to=cladisch@fastmail.net \
    --cc=alsa-devel@alsa-project.org \
    --cc=pharaoh137@gmail.com \
    /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.