Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Jan-Benedict Glaw <jbglaw@lug-owl.de>
To: William Estrada <MrUmunhum@popdial.com>
Cc: "alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>
Subject: Re: Using GDB for ALSA How to?
Date: Mon, 1 Sep 2008 22:24:07 +0200	[thread overview]
Message-ID: <20080901202407.GL15719@lug-owl.de> (raw)
In-Reply-To: <48BC4E6A.1070508@popdial.com>


[-- Attachment #1.1: Type: text/plain, Size: 751 bytes --]

On Mon, 2008-09-01 13:19:54 -0700, William Estrada <MrUmunhum@popdial.com> wrote:
>   I am trying to use GDB with my ALSA program. I wish to display (print) 
> a handle for
> an snd_pcm_t pointer. I am getting the following error:
> > (gdb) p Device
> > $9 = (snd_pcm_t *) 0x92be458
> > (gdb) p *Device
> > $10 = <incomplete type>
>   How do I display the snd_pcm_t structure?

My guess is that this pointer is simply uninitialized. Did you check
that it was properly prepared?

MfG, JBG

-- 
      Jan-Benedict Glaw      jbglaw@lug-owl.de              +49-172-7608481
Signature of:              What we do for ourselves dies with us. What we do for
the second  :         others and the world remains and is immortal. (Albert Pine)

[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

[-- Attachment #2: Type: text/plain, Size: 160 bytes --]

_______________________________________________
Alsa-devel mailing list
Alsa-devel@alsa-project.org
http://mailman.alsa-project.org/mailman/listinfo/alsa-devel

  reply	other threads:[~2008-09-01 20:24 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-01 20:19 Using GDB for ALSA How to? William Estrada
2008-09-01 20:24 ` Jan-Benedict Glaw [this message]
2008-09-01 20:33   ` William Estrada
2008-09-01 21:13     ` Jan-Benedict Glaw
2008-09-02  7:08       ` Jan-Benedict Glaw
2008-09-04 22:11         ` William Estrada

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=20080901202407.GL15719@lug-owl.de \
    --to=jbglaw@lug-owl.de \
    --cc=MrUmunhum@popdial.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox