All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugtrack@alsa-project.org
To: alsa-devel@alsa-project.org
Subject: [ALSA - lib 0001571]: Segfaults when trying to specify the preamble values (iec958 plugin)
Date: Thu, 17 Nov 2005 01:51:32 +0100	[thread overview]
Message-ID: <6d40b3f4e6168362126e41a6152468d2@bugtrack.alsa-project.org> (raw)


The following issue has been SUBMITTED.
======================================================================
<https://bugtrack.alsa-project.org/alsa-bug/view.php?id=1571> 
======================================================================
Reported By:                nboullis
Assigned To:                
======================================================================
Project:                    ALSA - lib
Issue ID:                   1571
Category:                   1_pcm - digital audio
Reproducibility:            always
Severity:                   minor
Priority:                   normal
Status:                     new
======================================================================
Date Submitted:             11-17-2005 01:51 CET
Last Modified:              11-17-2005 01:51 CET
======================================================================
Summary:                    Segfaults when trying to specify the preamble values
(iec958 plugin)
Description: 
When I try to specify the preamble values for the iec958 plugin (see the
attached .asoundrc file for an example), I get segfaults with all
applications that try to use the corresponding device. If I simply comment
out the 3 preamble lines, the application runs fine (well, not with the
null output, but with a real S/PDIF device) but I get no sound since I'm
not using the correct preamble values.

(This is with version 1.0.10.)

Here is a backtrace I got with valgrind (using xmms as the application):

==15761== 
==15761== Thread 5:
==15761== Invalid read of size 4
==15761==    at 0x1CADD3F7: snd_config_iterator_first (conf.c:3146)
==15761==    by 0x1CB373BB: _snd_pcm_iec958_open (pcm_iec958.c:623)
==15761==    by 0x1CAF9CB6: snd_pcm_open_conf (pcm.c:2070)
==15761==    by 0x1CAFA61A: snd_pcm_open_slave (pcm.c:2187)
==15761==    by 0x1CB1A32C: _snd_pcm_plug_open (pcm_plug.c:1140)
==15761==    by 0x1CAF9CB6: snd_pcm_open_conf (pcm.c:2070)
==15761==    by 0x1CAFA2BD: snd_pcm_open_noupdate (pcm.c:2102)
==15761==    by 0x1CAFA376: snd_pcm_open (pcm.c:2123)
==15761==    by 0x1CAB0E18: (within /usr/lib/xmms/Output/libALSA.so)
==15761==    by 0x1CAB09D1: alsa_open (in
/usr/lib/xmms/Output/libALSA.so)
==15761==    by 0x1CBB0469: (within /usr/lib/xmms/Input/libmpg123.so)
==15761==    by 0x1BAFFB62: start_thread (in /lib/tls/libpthread-0.60.so)
==15761==  Address 0x4 is not stack'd, malloc'd or (recently) free'd

Hope this helps.
======================================================================

Issue History
Date Modified  Username       Field                    Change              
======================================================================
11-17-05 01:51 nboullis       New Issue                                    
11-17-05 01:51 nboullis       File Added: .asoundrc                        
======================================================================




-------------------------------------------------------
This SF.Net email is sponsored by the JBoss Inc.  Get Certified Today
Register for a JBoss Training Course.  Free Certification Exam
for All Training Attendees Through End of 2005. For more info visit:
http://ads.osdn.com/?ad_id=7628&alloc_id=16845&op=click

             reply	other threads:[~2005-11-17  0:51 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-17  0:51 bugtrack [this message]
  -- strict thread matches above, loose matches on Subject: below --
2005-11-19  0:35 [ALSA - lib 0001571]: Segfaults when trying to specify the preamble values (iec958 plugin) bugtrack
2005-11-23 16:45 bugtrack
2005-11-23 16:46 bugtrack

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=6d40b3f4e6168362126e41a6152468d2@bugtrack.alsa-project.org \
    --to=bugtrack@alsa-project.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.